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

[Mark Wielaard]

Hi Jan (added Sam to CC),

On Mon, Aug 21, 2023 at 08:25:23AM +0200, Jan Beulich wrote:
> On 18.08.2023 23:54, 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/1142
> > 
> > Build state: failed test (failure)
> > Revision: b41ef0baac449de58c84d1a0261af0d91443b540
> > Worker: gentoo-sparc
> > Build Reason: (unknown)
> > Blamelist: Jan Beulich <jbeulich@suse.com>
> > 
> > Steps:
> [...]
> > - 5: make check ( failure )
> >     Logs:
> >         - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/1142/steps/5/logs/stdio
> 
> Looking just here - where's the failure indication, other than an unhelpful
> "timed out"? (I believe this isn't the first time I'm observing such a
> report.)

Clearly something hung in the testsuite. Sometimes you can find
additional logs in the full build steps here:

https://builder.sourceware.org/buildbot/#builders/228/builds/1142

And if that doesn't give a clue (it doesn't in this case), you can
look for the Upload to bunsen step, which contains an URL to the
bunsen entry containing all log files and full results, in this case:

https://builder.sourceware.org/testrun/02dd95c110a6d72025efd682e0614fac3bd7ee13

The filelist normally contains some logs that can be helpful.

But I don't see anything specific in this case either.  So then we ask
the person running the buildbot sparc builder, which is Sam (CCed).

All the builds after this one seem green. So maybe the buildbot worker
was just really slow?

Cheers,

Mark