public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Mark Wielaard <mark@tarox.wildebeest.org>, gdb-testers@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>, Jan Beulich <jbeulich@suse.com>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed test (failure) (master)
Date: Wed, 18 May 2022 17:30:00 +0100 [thread overview]
Message-ID: <78ccb806-0734-bded-285a-486b89bb0481@arm.com> (raw)
In-Reply-To: <20220518134526.GA13942@tarox.wildebeest.org>
Hi Mark,
I think it's the right thing to do. Let's keep it disabled for now until we can understand/fix the problem.
We don't want this particular issue to compromise the quality of the reports.
On 5/18/22 14:45, Mark Wielaard wrote:
> Hi,
>
> On Wed, May 18, 2022 at 01:02:36PM +0000, builder@sourceware.org wrote:
>> A new failure has been detected on builder gdb-debian-armhf while building binutils-gdb.
>>
>> Full details are available at:
>> https://builder.sourceware.org/buildbot/#builders/72/builds/210
>>
>> Build state: failed test (failure)
>> Revision: 4bb8b8e9381bce9734454470ebd1572534e7514e
>> Worker: debian-armhf
>> Build Reason: (unknown)
>> Blamelist: Jan Beulich <jbeulich@suse.com>, Nick Clifton <nickc@redhat.com>
>> [...]
>> - 5: make check-gdb ( failure )
>> Logs:
>> - stdio: https://builder.sourceware.org/buildbot/#builders/72/builds/210/steps/5/logs/stdio
>> - gdb.sum: https://builder.sourceware.org/buildbot/#builders/72/builds/210/steps/5/logs/gdb_sum
>> - gdb.log: https://builder.sourceware.org/buildbot/#builders/72/builds/210/steps/5/logs/gdb_log
>
> Sigh. Sorry about that. Apparently make gdb-check is flaky on debian-armhf.
> See also https://sourceware.org/bugzilla/show_bug.cgi?id=28561
>
> I have disabled the gdb-check on armhf for now.
>
> Cheers,
>
> Mark
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2022-05-18 16:30 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 13:02 builder
2022-05-18 13:45 ` Mark Wielaard
2022-05-18 16:30 ` Luis Machado [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-11 1:01 builder
2022-12-22 4:09 builder
2022-12-15 0:31 builder
2022-12-06 15:13 builder
2022-11-28 16:22 builder
2022-11-28 16:18 builder
2022-11-22 0:29 builder
2022-11-11 15:20 builder
2022-11-07 16:53 builder
2022-10-26 12:16 builder
2022-10-26 7:45 builder
2022-10-18 15:33 builder
2022-10-16 19:01 builder
2022-10-16 18:51 builder
2022-10-16 17:51 builder
2022-10-16 17:23 builder
2022-10-16 17:23 builder
2022-10-16 17:19 builder
2022-10-16 17:15 builder
2022-10-16 17:05 builder
2022-09-13 12:20 builder
2022-09-12 8:31 builder
2022-08-31 18:22 builder
2022-08-31 17:30 builder
2022-08-03 20:03 builder
2022-07-30 0:27 builder
2022-07-29 7:49 builder
2022-07-19 14:54 builder
2022-07-15 17:52 builder
2022-07-15 0:19 builder
2022-07-08 14:07 builder
2022-06-07 18:34 builder
2022-05-31 15:39 builder
2022-05-18 0:23 builder
2022-05-17 10:50 builder
2022-05-17 5:52 builder
2022-05-15 0:25 builder
2022-05-13 20:18 builder
2022-05-15 15:04 ` Mark Wielaard
2022-05-16 8:25 ` Luis Machado
2022-05-16 8:44 ` Mark Wielaard
2022-05-16 9:12 ` Luis Machado
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=78ccb806-0734-bded-285a-486b89bb0481@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-testers@sourceware.org \
--cc=jbeulich@suse.com \
--cc=mark@tarox.wildebeest.org \
--cc=nickc@redhat.com \
/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).