On Fri, Nov 22, 2024 at 03:51:10AM +0000, buil...@sourceware.org wrote: > A new failure has been detected on builder elfutils-debian-amd64 while > building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#/builders/52/builds/427 > > Build state: failed test (failure) > Revision: 5cc89c78499cd37465d7b0b3f35ef0e5d07a98cc > Worker: bb1-2 > Build Reason: (unknown) > Blamelist: Mark Wielaard <m...@klomp.org> > > - 7: make check ( failure ) > Logs: > - stdio: > https://builder.sourceware.org/buildbot/#/builders/52/builds/427/steps/7/logs/stdio > - test-suite.log: > https://builder.sourceware.org/buildbot/#/builders/52/builds/427/steps/7/logs/test-suite_log
The tests are ran under valgrind which seems to crash with an assertion failure: valgrind: m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed. This should have been fixed by: https://bugs.kde.org/show_bug.cgi?id=465435 commit e61a04babcc3de8c1c86638f8ccdb4ef1b74a4d0 Author: Paul Floyd <pjfl...@wanadoo.fr> Date: Fri Feb 24 21:31:35 2023 +0100 bug465435 - m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed. Although that might just point out that we are running under docker and so this would still fail with: + if (newfd == -1) { + VG_(debugLog)(0, "libcfile", "Valgrind: FATAL: " + "Private file creation failed.\n" + " The current file descriptor limit is %d.\n" + " If you are running in Docker please consider\n" + " lowering this limit with the shell built-in limit command.\n", + VG_(fd_hard_limit)); + VG_(debugLog)(0, "libcfile", "Exiting now.\n"); + VG_(exit)(1); + } I'll look if I can adjust the buildbot docker environment if this is the case. Cheers, Mark
