☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)

[Mark Wielaard]

Hi Jan (CC Sam and builbot mailinglist),

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.

Sam, could you please let us know when the sparc builder is a little
bit more robust so we can reactivate the email notifications again?

Thanks,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Change-tags-on-binutils-gentoo-sparc-builders-to-bin.patch
Type: text/x-patch
Size: 1343 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20231019/634d345f/attachment.bin>