Hi,
On Tue, 2023-05-09 at 12:05 +0000, builder--- via Elfutils-devel 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/67
>
> Build state: failed test (failure)
> Revision: e65bbdde97f4094274dbdc327147e9cfe1fcc9a0
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: Youling Tang <tangyoul...@loongson.cn>
>
> Steps:
> [...]
>
> - 7: make check ( failure )
> Logs:
> - stdio:
> https://builder.sourceware.org/buildbot/#builders/225/builds/67/steps/7/logs/stdio
> - test-suite.log:
> https://builder.sourceware.org/buildbot/#builders/225/builds/67/steps/7/logs/test-suite_log
Sigh, sparc again. Now run-debuginfod-regex.sh FAILs because
thread_work_total{role="groom"} never gets to 1.
I don't really understand this. And again this cannot be caused by the
last commit (backends: Add set_initial_registers_tid callback for
LoongArch).
I will assume this is a flaky test (or maybe sparc is flaky?)
Cheers,
Mark
