Hello, When built under a very loaded system, ell may fail its test suite in a nondeterministic fashion like so:
--8<---------------cut here---------------start------------->8--- --- ./test-suite.log -------------------------------------------------------- ================================ ell 0.41: ./test-suite.log ================================ # TOTAL: 40 # PASS: 38 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unit/test-dbus-message-fds ================================ launching dbus-daemon dbus-daemon process 16906 created ready request name result=failed TEST: FD passing 1 TEST FAILED in get_random_return_callback at unit/test-dbus-message-fds.c:278: !l_dbus_message_get_error(message, ((void *)0), ((void *)0)) Disconnected from DBus FAIL unit/test-dbus-message-fds (exit status: 134) FAIL: unit/test-dbus-properties =============================== launching dbus-daemon dbus-daemon process 16899 created ready request name result=success TEST: Legacy properties get TEST: Legacy properties set TEST: Legacy optional property TEST: org.freedesktop.DBus.Properties get TEST: org.freedesktop.DBus.Properties set TEST: Property changed signals Disconnected from DBus FAIL unit/test-dbus-properties (exit status: 134) error: in phase 'check': uncaught exception: %exception #<&invoke-error program: "make" arguments: ("check" "-j" "24") exit-status: 2 term-signal: #f stop-signal: #f> phase `check' failed after 46.2 seconds command "make" "check" "-j" "24" failed with status 2 --8<---------------cut here---------------end--------------->8--- I've had this occur twice so far, always when the build machine is busy building multiple things in parallel. I suspect a dbus timeout or similar. Maxim