From: Simon Marchi <simark@simark.ca>
To: Jan Vrany <jan@vrany.io>, GDB mailing list <gdb@sourceware.org>
Subject: Re: CI scripts
Date: Wed, 18 Jan 2023 11:04:54 -0500 [thread overview]
Message-ID: <164b7d9a-03a9-1256-56c5-48f1327bfe28@simark.ca> (raw)
In-Reply-To: <29aa46326e96d373dff8c20d0ad5d9c948d05a7c.camel@vrany.io>
> After updating the repo from your fork to upstream I do see loads of failures
> as well. Once fixed, it should get back to normal for me too.
Almost!
Before that I had these failures:
FAIL: gdb.dap/basic-dap.exp: disassemble one instruction success
FAIL: gdb.dap/basic-dap.exp: instructions in disassemble output
They would be fixed by that series:
https://inbox.sourceware.org/gdb-patches/20230106185729.42372-1-simon.marchi@efficios.com/
And often some gdb.threads/detach-step-over.exp internal errors. Since
gdb.threads/detach-step-over.exp is a new-ish test, I'd like to avoid
marking it as "known fail", and actually fix the problem. The goal is
for that list to shrink, not grow :).
Simon
next prev parent reply other threads:[~2023-01-18 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 12:56 Jan Vrany
2023-01-12 13:55 ` Simon Marchi
2023-01-18 12:09 ` Jan Vrany
2023-01-18 13:36 ` Simon Marchi
2023-01-18 16:00 ` Jan Vrany
2023-01-18 16:04 ` Simon Marchi [this message]
2023-01-19 2:42 ` Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164b7d9a-03a9-1256-56c5-48f1327bfe28@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=jan@vrany.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).