Control: retitle -1 ostree: libostree/test-concurrency.py.test intermittently
fails: opendir(staging-$RANDOM): No such file or directory
Control: forwarded -1 https://github.com/ostreedev/ostree/issues/1620
On Sat, 09 Jun 2018 at 20:25:46 +0200, Paul Gevers wrote:
> While inspecting regressions in autopkgtest results¹, I noticed that
> your package ostree version 2018.5-1 failed twice²³ with a spurious error
More specifically: libostree/test-concurrency.py.test failed. I suspect
that this indicates a race condition in libostree, or possibly a race
condition in that test.
When reporting test failures, would it be possible to try to pick out
the failing test name, and put the common features of the failures in
the bug report's Subject? I'd prefer to make sure each flaky test/reason
for flakiness has a bug report, rather than mixing up multiple issues
under one bug number.
smcv
