Re: [PATCH] tests: Don't set DEBUGINFOD_TIMEOUT
Hi, On Thu, 2021-11-11 at 15:46 +0100, Mark Wielaard wrote: > Various tests set DEBUGINFOD_TIMEOUT to 10. Which is less than the default > of 90. None of the tests relied on a lower timeout. So just don't set it. Pushed. Cheers, Mark
Buildbot failure in Wildebeest Builder on whole buildset
The Buildbot has detected a new failure on builder elfutils-centos-x86_64 while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/1/builds/860 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: centos-x86_64 Build Reason: Blamelist: Mark Wielaard BUILD FAILED: failed test (failure) Sincerely, -The Buildbot
Re: Buildbot failure in Wildebeest Builder on whole buildset
On Mon, 2021-11-15 at 10:56 +, build...@builder.wildebeest.org wrote: > The Buildbot has detected a new failure on builder elfutils-centos- > x86_64 while building elfutils. > Full details are available at: > https://builder.wildebeest.org/buildbot/#builders/1/builds/860 > > Buildbot URL: https://builder.wildebeest.org/buildbot/ > > Worker for this Build: centos-x86_64 I am not sure why this failed. The make check timed out because there wasn't any output for 20 minutes. Even though this is with valgrind no test really should take that long.
[Bug libdw/26696] Support SVE dwarf
https://sourceware.org/bugzilla/show_bug.cgi?id=26696 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org --- Comment #1 from Mark Wielaard --- These are now described here: https://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/22253] RFE elfutils add man pages documenting the API
https://sourceware.org/bugzilla/show_bug.cgi?id=22253 --- Comment #2 from Mark Wielaard --- (In reply to Mark Wielaard from comment #1) > These are now described here: > https://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst > > In particular the Z registers aren't yet described in > backends/aarch64_regs.c > and neither is the Vector granule pseudo register. Sorry that was for a different bug: https://sourceware.org/bugzilla/show_bug.cgi?id=26696 -- You are receiving this mail because: You are on the CC list for the bug.