Source: dbus Version: 1.11.16+really1.11.16-2 Severity: normal (X-Debbugs-Cc to debian-hurd)
I recently enabled build-time tests for dbus, after fixing the home directory issue that had previously meant they failed on all Debian buildds. Unfortunately this led to a build failure on hurd-i386. Because it's reasonably clear that nobody with an interest in Hurd is currently contributing to dbus upstream, and the test results indicate that dbus does basically work, I'm going to ignore the test failures on !linux for the moment. The bug I'm describing in this bug report manifests as a failure of the test case test-refs: > (/<<BUILDDIR>>/dbus-1.11.16+really1.11.16/debian/build-main/test/.libs/test-refs:11704): > GLib-ERROR **: creating thread '': Error creating thread: Resource > temporarily unavailable > ../../../build-aux/tap-driver.sh: line 639: 11704 Trace/breakpoint trap "$@" > # random seed: R02S2177400da32c2ff3132d8939e29fddec > 1..4 > # Start of refs tests > # GLib-FATAL-ERROR: creating thread '': Error creating thread: Resource > temporarily unavailable > ERROR: test-refs - too few tests run (expected 4, got 0) > ERROR: test-refs - exited with status 133 (terminated by signal 5?) For context, test-refs is a stress-test intended to confirm that the atomic operations that we use for thread-safe reference counting are actually working. S