From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Fri, 11 Nov 2022 18:48:17 +0100 [thread overview]
Message-ID: <61627617-d385-1e81-2220-baae64291dcb@suse.de> (raw)
In-Reply-To: <82af09dc0785ff4cd6076664ea8fb8adb87f08ca.camel@klomp.org>
On 11/11/22 18:14, Mark Wielaard wrote:
> Hi Tom,
>
> On Mon, 2022-09-12 at 10:46 +0200, Tom de Vries wrote:
>> On 9/12/22 10:31, builder@sourceware.org wrote:
>>> A new failure has been detected on builder gdb-fedora-x86_64 while
>>> building binutils-gdb.
>>>
>>> Full details are available at:
>>>
>>> https://builder.sourceware.org/buildbot/#builders/74/builds/1088
>>>
>>> Build state: failed test (failure)
>>
>> I looked at gdb.log, and found these FAILs:
>> ...
>> (gdb) maintenance selftest copy\a_\a
>> copy_bitwise copy_integer_to_size
>> (gdb) maintenance selftest copy_PASS: gdb.gdb/unittest.exp:
>> test_completion: tab complete "maintenance selftest copy"
>> FAIL: gdb.gdb/unittest.exp: test_completion: tab complete
>> "maintenance
>> selftest copy" (clearing input line) (timeout)
>> ^Cmaintenance selftest copy_bit\aQuit
>> (gdb) FAIL: gdb.gdb/unittest.exp: test_completion: tab complete
>> "maintenance selftest copy_bit"
>> Quit
>> ...
>>
>> This looks like the well-known
>> https://sourceware.org/bugzilla/show_bug.cgi?id=27813 to me.
>>
>> Maybe we should move the completion tests out of this test-case?
>
> Saw this fail a couple of other times as well. Latest:
> https://builder.sourceware.org/buildbot/#builders/170/builds/1088
>
Hi Mark,
I did look at that failure, but the failure mode is different:
...
(gdb) maintenance selftest copy\a_\a
copy_bitwise copy_integer_to_size
FAIL: gdb.gdb/unittest.exp: test_completion: tab complete "maintenance
selftest copy" (second tab) (timeout)
Quit
...
I don't know what's causing that. Maybe some system readline vs. gdb
readline issue, just a guess.
> Do you propose to split out the test_completion from
> gdb.gdb/unittest.exp or to just remove it from the list of TESTS for
> the buildbot make check-gdb target?
The first.
Thanks,
- Tom
prev parent reply other threads:[~2022-11-11 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220912083142.E79913857004@sourceware.org>
2022-09-12 8:46 ` Tom de Vries
2022-11-11 17:14 ` Mark Wielaard
2022-11-11 17:48 ` Tom de Vries [this message]
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=61627617-d385-1e81-2220-baae64291dcb@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=simon.marchi@polymtl.ca \
/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).