Control: severity -1 serious On Thu, Nov 06, 2025 at 11:29:11AM +0800, Chow Loong Jin wrote: > Control: severity -1 important > Control: tags -1 + unreproducible > > Hi, > > I'm unable to reproduce this build failure either on my machine via > sbuild, or in an amd64 porter box (barriere.debian.org). I've uploaded > my build log for you to have a look, and the relevant part of the build > log diff seems to be as follows: > > -1: [==========] 148 tests from 58 test suites ran. (2 ms total) > +1: [==========] 148 tests from 58 test suites ran. (5 ms total) > 1: [ PASSED ] 148 tests. > 1/2 Test #1: sdbus-c++-unit-tests ............. Passed 0.01 sec > test 2 > Start 2: sdbus-c++-integration-tests > > -2: Test command: > /build/reproducible-path/sdbus-cpp-2.1.0/obj-x86_64-linux-gnu/tests/sdbus-c++-integration-tests > -2: Working Directory: > /build/reproducible-path/sdbus-cpp-2.1.0/obj-x86_64-linux-gnu/tests > +2: Test command: > /home/hyperair/sdbus-cpp/sdbus-cpp-2.1.0/obj-x86_64-linux-gnu/tests/sdbus-c++-integration-tests > +2: Working Directory: > /home/hyperair/sdbus-cpp/sdbus-cpp-2.1.0/obj-x86_64-linux-gnu/tests > 2: Test timeout computed to be: 10000000 > -2: terminate called after throwing an instance of 'sdbus::Error' > -2: what(): [org.freedesktop.DBus.Error.FileNotFound] Failed to open bus > (No such file or directory) > -2/2 Test #2: sdbus-c++-integration-tests ......Subprocess > aborted***Exception: 0.01 sec > -terminate called after throwing an instance of 'sdbus::Error' > - what(): [org.freedesktop.DBus.Error.FileNotFound] Failed to open bus (No > such file or directory) > - > - > -50% tests passed, 1 tests failed out of 2 > - > -Total Test time (real) = 0.01 sec > - > -The following tests FAILED: > - 2 - sdbus-c++-integration-tests (Subprocess aborted) > -Errors while running CTest > -make[2]: *** [Makefile:94: test] Error 8 > -make[2]: Leaving directory > '/build/reproducible-path/sdbus-cpp-2.1.0/obj-x86_64-linux-gnu' > -dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test > ARGS\+=--verbose ARGS\+=-j1 returned exit code 2 > -make[1]: *** [debian/rules:24: override_dh_auto_test-arch] Error 25 > -make[1]: Leaving directory '/build/reproducible-path/sdbus-cpp-2.1.0' > -make: *** [debian/rules:14: binary] Error 2 > -dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 > --------------------------------------------------------------------------------- > -Build finished at 2025-09-19T11:25:22Z > +2: [==========] Running 190 tests from 12 test suites. > +2: [----------] Global test environment set-up. > +2: [----------] 5 tests from Connection > +2: [ RUN ] Connection.CanBeDefaultConstructed > +2: [ OK ] Connection.CanBeDefaultConstructed (0 ms) > +2: [ RUN ] Connection.CanRequestName > +2: [ OK ] Connection.CanRequestName (1 ms) > +2: [ RUN ] Connection.CanReleaseRequestedName > +2: [ OK ] Connection.CanReleaseRequestedName (1 ms) > +2: [ RUN ] Connection.CannotReleaseNonrequestedName > +2: [ OK ] Connection.CannotReleaseNonrequestedName (0 ms) > +2: [ RUN ] Connection.CanEnterAndLeaveInternalEventLoop > +2: [ OK ] Connection.CanEnterAndLeaveInternalEventLoop (1 ms) > +2: [----------] 5 tests from Connection (5 ms total) > > Judging by how sdbus-cpp relies on a fixed path in /tmp for its > dbus-daemon config files and socket[1], I think that maybe a concurrent > build wiped it out in a shared /tmp directory on your end? Either that > or maybe /tmp isn't writable in your chroot for some reason. >...
It did now also happen twice on the ppc64el buildds[1] (and on some non-release architectures). There is only one build running on a buildd at a time, which rules out the "concurrent build" theory. > Kind regards, > Loong Jin cu Adrian [1] https://buildd.debian.org/status/logs.php?pkg=sdbus-cpp&ver=2.1.0-1%2Bb1&arch=ppc64el&suite=sid
