* Buildbot failure in Wildebeest Builder on whole buildset
@ 2020-01-17 0:08 buildbot
2020-01-17 11:12 ` Spurious run-debuginfod-find.sh failure on ppc64le (Was: Buildbot failure in Wildebeest Builder on whole buildset) Mark Wielaard
0 siblings, 1 reply; 2+ messages in thread
From: buildbot @ 2020-01-17 0:08 UTC (permalink / raw)
To: elfutils-devel
The Buildbot has detected a failed build on builder whole buildset while building elfutils.
Full details are available at:
https://builder.wildebeest.org/buildbot/#builders/11/builds/412
Buildbot URL: https://builder.wildebeest.org/buildbot/
Worker for this Build: fedora-ppc64le
Build Reason: <unknown>
Blamelist: Mark Wielaard <mark@klomp.org>
BUILD FAILED: failed test (failure)
Sincerely,
-The Buildbot
^ permalink raw reply [flat|nested] 2+ messages in thread
* Spurious run-debuginfod-find.sh failure on ppc64le (Was: Buildbot failure in Wildebeest Builder on whole buildset)
2020-01-17 0:08 Buildbot failure in Wildebeest Builder on whole buildset buildbot
@ 2020-01-17 11:12 ` Mark Wielaard
0 siblings, 0 replies; 2+ messages in thread
From: Mark Wielaard @ 2020-01-17 11:12 UTC (permalink / raw)
To: elfutils-devel
Hi,
On Fri, 2020-01-17 at 00:08 +0000, buildbot@builder.wildebeest.org
wrote:
> The Buildbot has detected a failed build on builder whole buildset
> while building elfutils.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/11/builds/412
>
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>
> Worker for this Build: fedora-ppc64le
This is a failure of run-debuginfod-find.sh only on this particular
worker which identifies as:
Fedora release 30 (Thirty)
Linux 5.2.9-200.fc30.ppc64le #1 SMP Fri Aug 16 21:03:00 UTC 2019
GNU C Library (GNU libc) stable release version 2.29.
g++ 9.1.1
binutils 2.31.1
configured with:
./configure --enable-maintainer-mode --enable-sanitize-undefined --
disable-valgrind
I have not been able to replicate the failure on the exact same setup.
The end of the log looks like:
metric ready: 1
Wait 20 seconds on 9380 for metric thread_work_total{role="traverse"} to change to 1
metric thread_work_total{role="traverse"}: 1
Wait 20 seconds on 9380 for metric thread_work_pending{role="scan"} to change to 0
metric thread_work_pending{role="scan"}: 0
Wait 20 seconds on 9380 for metric thread_busy{role="scan"} to change to 0
metric thread_busy{role="scan"}: 0
dpkg-deb is /usr/bin/dpkg-deb
'/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/debuginfod-debs/hithere-dbgsym_1.0-1_amd64.ddeb' -> 'D/hithere-dbgsym_1.0-1_amd64.ddeb'
'/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/debuginfod-debs/hithere_1.0-1_amd64.deb' -> 'D/hithere_1.0-1_amd64.deb'
Wait 20 seconds on 9380 for metric scanned_total{source=".deb archive"} to change to 1
metric scanned_total{source=".deb archive"}: 0
[Thu Jan 16 22:54:37 2020] (7936/7945): fts traversed source paths in 0.000347s, scanned=7, regex-skipped=0
metric scanned_total{source=".deb archive"}: 1
Wait 20 seconds on 9380 for metric scanned_total{source=".ddeb archive"} to change to 1
metric scanned_total{source=".ddeb archive"}: 1
/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/test-7446/.client_cache2/20775d302a6b5fc57259590d09b2198417e9bc2c/debuginfo
L/foo: symbolic link to /home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/dwfllines
L/foo: ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), dynamically linked, interpreter /lib64/ld64.so.2, for GNU/Linux 3.10.0, BuildID[sha1]=431e178587ec40aced99356843045d02d8f1ed69, with debug_info, not stripped
[Thu Jan 16 22:54:37 2020] (7458/8037): not found
Server query failed: No such file or directory
[Thu Jan 16 22:54:37 2020] (7458/8040): not found
[Thu Jan 16 22:54:37 2020] (7936/8039): libc error: upstream debuginfod query failed: No such file or directory
Server query failed: No such file or directory
FAIL run-debuginfod-find.sh (exit status: 1)
Full test-suite.log is at:
https://builder.wildebeest.org/buildbot/#/builders/11/builds/412/steps/8/logs/test-suite_log
Anyone a guess what is going on in this case?
Thanks,
Mark
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-01-17 11:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-17 0:08 Buildbot failure in Wildebeest Builder on whole buildset buildbot
2020-01-17 11:12 ` Spurious run-debuginfod-find.sh failure on ppc64le (Was: Buildbot failure in Wildebeest Builder on whole buildset) Mark Wielaard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).