Skip to content

tests/liblal-test: fail fast when old GDBusConnection lingers

Ratchanan Srirattanamet requested to merge personal/peat-psuwit/bus-failfast into main

I now understand what the "wait for destroyed GDBusConnection" test is for: to make sure the next test pick up the new DBus daemon address. To properly fixes this is to re-structure how the tests are conducted. So, I attacked it from the other perspective.

We already consider this test flaky, and re-run the test 3 times. So, I gives the test more attempts, and to also make sure the test itself quits early if this failure mode happens. While this doesn't make the test more reliable, at least makes it less likely to block, and more likely to pass, in CI.

Related: #6

Merge request reports