From: Jan Beulich <jbeulich@suse.com>
To: Mark Wielaard <mark@klomp.org>
Cc: binutils@sourceware.org, Sam James <sam@gentoo.org>,
buildbot@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)
Date: Thu, 19 Oct 2023 13:48:15 +0200 [thread overview]
Message-ID: <8e9bafaa-f56d-e769-60e4-f0969e268cc1@suse.com> (raw)
In-Reply-To: <37994c7987bb6fd75ad4ee36a1029d8b05b7d11e.camel@klomp.org>
On 19.10.2023 13:23, Mark Wielaard wrote:
> On Mon, 2023-10-16 at 08:48 +0200, Jan Beulich wrote:
>> On 13.10.2023 02:42, builder@sourceware.org wrote:
>>> A new failure has been detected on builder binutils-gentoo-sparc while building binutils-gdb.
>>>
>>> Full details are available at:
>>> https://builder.sourceware.org/buildbot/#builders/228/builds/1402
>>>
>>> Build state: failed test (failure)
>>> Revision: 59fed66dcef07b7b33c72d47b609e05569c62523
>>> Worker: gentoo-sparc
>>> Build Reason: (unknown)
>>
>> Imo the rate of fails (iirc unexplained timeouts) is too high here. May
>> I ask that this worker be taken out, until the issue can be sorted?
>
> I have applied the attached patch which keeps the binutils sparc
> builder, but changes the tag from binutils to binutils-build. This
> makes it so that it won't be part of the binutils CI reports (so no
> more email notifications), but still runs the build which will show up
> on https://builder.sourceware.org/buildbot/ and get the results into
> bunsen.
>
> I did the same for the binutils-try-gentoo-sparc builder (changing the
> tag from binutils-try to binutils-try-build). So for try builds you
> won't get emails about the sparc builder anymore, but the results will
> show up on the builder website and in bunsen.
Thanks for doing this.
Jan
prev parent reply other threads:[~2023-10-19 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231013004211.102B03858436@sourceware.org>
[not found] ` <15888d31-891a-8c70-26c2-8ff860799d14@suse.com>
2023-10-19 11:23 ` Mark Wielaard
2023-10-19 11:48 ` Jan Beulich [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=8e9bafaa-f56d-e769-60e4-f0969e268cc1@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
--cc=sam@gentoo.org \
/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).