On Fri, May 27, 2022 at 04:02:41PM +0000, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-centos-x86_64 while
> building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/39/builds/31
>
> Build state: failed test (failure)
> Revision: b8713b3fd0617415c76df8c9da70f8e2f26d3134
> Worker: centos-x86_64
> Build Reason: (unknown)
> Blamelist: Mark Wielaard <[email protected]>
>
> Steps:
> [...]
> - 7: make check ( failure )
> Logs:
> - stdio:
> https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/7/logs/stdio
> - test-suite.log:
> https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/7/logs/test-suite_log
The failure comes from run-debuginfod-federation-metrics.sh, this
part:
# Trigger a flood of requests against the same archive content file.
# Use a file that hasn't been previously extracted in to make it
# likely that even this test debuginfod will experience concurrency
# and impose some "after-you" delays.
(for i in `seq 100`; do
curl -s
http://127.0.0.1:$PORT1/buildid/87c08d12c78174f1082b7c888b3238219b0eb265/executable
>/dev/null &
done;
wait)
curl -s http://127.0.0.1:$PORT1/metrics | grep 'http_responses_after_you.*'
Where the error is:
+ curl -s http://127.0.0.1:9025/metrics
+ grep 'http_responses_after_you.*'
/srv/buildbot/worker/elfutils-centos-x86_64/build/tests/run-debuginfod-federation-metrics.sh:
line 198: 27160 Aborted (core dumped) env
LD_LIBRARY_PATH=$ldpath ${abs_builddir}/../debuginfod/debuginfod $VERBOSE -d
${DB} -F -U -t0 -g0 -p $PORT1 L D F > vlog$PORT1 2>&1
++ err
++ trap - ERR
++ echo ERROR REPORTS
This doesn't really make sense to me. Sadly the test machine doesn't actually
have a core file:
Process 27160 (debuginfod) of user 994 killed by SIGABRT - ignoring (low free
space)
Lets see what happens on a rebuild.
Cheers,
Mark