Hi,

On Wed, 2023-11-01 at 15:08 +0000, builder@sourceware.org wrote:
> A new failure has been detected on builder elfutils-gentoo-sparc while building elfutils.
> 
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#builders/225/builds/115
> 
> Build state: failed test (failure)
> Revision: c112cf0f1975e19a6111f594c0e5c4d2210c0f9a
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: Omar Sandoval <osandov@fb.com>
> 
> Steps:
> 
> - 7: make check ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#builders/225/builds/115/steps/7/logs/stdio
>         - test-suite.log: https://builder.sourceware.org/buildbot/#builders/225/builds/115/steps/7/logs/test-suite_log

   command timed out: 1200 seconds without output running [b'make',
   b'check', b'-j8', b'--output-sync=line'], attempting to kill
   process killed by signal 9
   program finished with exit code -1
   elapsedTime=1289.277272
   
So that is the sparc builder getting stuck again. Not caused by Omar's
patch.

I have applied the attached patch which keeps the elfutils sparc
builder, but changes the tag from elfutils to elfutils-build. This
makes it so that it won't be part of the elfutils 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 elfutils-try-gentoo-sparc builder (changing the
tag from elfutils-try to elfutils-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