It turned out that this has happened in the past and then resolved, so this is
a comeback.
For "dee" we can bump the timeout or skip the test on riscv64 for the immediate
problem
But the "dbus-test-runner timeout makes riscv64 builds" hang is a problem on
its own.
Therefore I added a bug task t
When lowering the timeout to trigger the same on x86 (to see if the hang
occurs there as well) I can see that the test breaks as it does on
riscv64, but the hang does not happen.
task-0: /Model/Transaction/Target2ChangeRemoveAppend:
OK
** (dbus-test-runner:15767): WARNING **: 11:26:03.671: Timi
Good case:
task-0: Shutting down
DBus daemon: Shutdown
make[4]: Leaving directory '/<>/dee-1.2.7+17.10.20170616/tests'
Bad case:
task-0: /ModelTags/SharedModel/TwoTags: OK
** (dbus-test-runner:2028709): WARNING **: 12:41:16.457: Timing out at
maximum wait of 60 seconds.
(dbus-test-runner:20287
If you catch the log at the right time there is a related test failure:
** (dbus-test-runner:1577514): WARNING **: 12:15:11.723: Timing out at maximum
wait of 60 seconds.
(dbus-test-runner:1577514): libdbustest-CRITICAL **: 12:15:11.736:
dbus_test_service_run: assertion 'all_tasks(service, all_t
FYI - I'm driving soem debugging enabled test builds at
https://launchpad.net/~paelzer/+archive/ubuntu/dee-groovy-hang/+packages
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4192/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
