Hi Sam, I think only the last one can really be said to be "your issue".
On Thu, 2023-07-20 at 11:37 +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/212 > > Build state: failed test (failure) > Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39 > Worker: centos-x86_64 > Build Reason: (unknown) > Blamelist: Sam James <s...@gentoo.org> > > - 7: make check ( failure ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/7/logs/stdio > - test-suite.log: > https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/7/logs/test-suite_log This is odd. Certainly not caused by your patch: FAIL: run-backtrace-native-core.sh dwfl_thread_getframes: no matching address range backtrace: backtrace.c:81: callback_verify: Assertion `seen_main' failed. This is a centos7 box/kernel. We have seen this before, but not recently. It might just be a "buggy" core file generated. > A new failure has been detected on builder elfutils-debian-ppc64 while > building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/63/builds/212 > > Build state: failed test (failure) > Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39 > Worker: debian-ppc64 > Build Reason: (unknown) > Blamelist: Sam James <s...@gentoo.org> > buildbot/#builders/63/builds/212/steps/6/logs/warnings__3_ > > - 7: make check ( failure ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/7/logs/stdio > - test-suite.log: > https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/7/logs/test-suite_log > > A new failure has been detected on builder elfutils-debian-testing-x86_64 > while building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/145/builds/172 > > Build state: failed test (failure) test (failure) > Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39 > Worker: bb1-1 > Build Reason: (unknown) > Blamelist: Sam James <s...@gentoo.org> > > - 7: make check ( failure ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#builders/145/builds/172/steps/7/logs/stdio > - test-suite.log: > https://builder.sourceware.org/buildbot/#builders/145/builds/172/steps/7/logs/test-suite_log These two builder are both running debian testing, which picked up a bad binutils: https://inbox.sourceware.org/binutils/20230713215808.ga11...@gnu.wildebeest.org/ Hopefully this gets resolved soon with a newer binutils snapshot. > A build exception has been detected on builder elfutils-gentoo-sparc while > building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/225/builds/84 > > Build state: exception update (exception) > Revision: (unknown) > Worker: gentoo-sparc > Build Reason: (unknown) > Blamelist: Sam James <s...@gentoo.org> > > Steps: > > - 0: worker_preparation ( success ) > > - 1: set package name ( success ) > > - 2: git checkout ( exception ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#builders/225/builds/84/steps/2/logs/stdio > - err.text: > https://builder.sourceware.org/buildbot/#builders/225/builds/84/steps/2/logs/err_text > - err.html: > https://builder.sourceware.org/buildbot/#builders/225/builds/84/steps/2/logs/err_html > This is your buildbot builder. Please kick it! :) Cheers, Mark
