This recently showed up often enough that I bothered to find this bug :-/
I think it degraded again into a state where we should consider:
IRC:
[13:16] <cpaelzer> Was there any hope to not expect this to be a retry-monster forever?
[13:17] <Laney> The desktop team should be asked if they can work on making that less flaky
[13:17] <Laney> I don't think ignoring the tests there is a good answer
[13:18] <Laney> Reducing the coverage would be preferable if that gets it to be more stable, for example, assuming the flakiness can't be easily fixed
I have a simple test stats gatherer [1] that also shows the subtests which helps a lot in those cases to identify potential candidates to skip.
I attached the output, best viewed in monospace
AFAICS up until recently we had <15% on all architectures.
But in Hirsute on arm* I see a bump to 22% of the subtest "uicheck-sw".
Could be bad-luck / noise - but maybe it is worth considering to skip that on arm?
This recently showed up often enough that I bothered to find this bug :-/
I think it degraded again into a state where we should consider:
IRC:
[13:16] <cpaelzer> Was there any hope to not expect this to be a retry-monster forever?
[13:17] <Laney> The desktop team should be asked if they can work on making that less flaky
[13:17] <Laney> I don't think ignoring the tests there is a good answer
[13:18] <Laney> Reducing the coverage would be preferable if that gets it to be more stable, for example, assuming the flakiness can't be easily fixed
I have a simple test stats gatherer [1] that also shows the subtests which helps a lot in those cases to identify potential candidates to skip.
I attached the output, best viewed in monospace
AFAICS up until recently we had <15% on all architectures.
But in Hirsute on arm* I see a bump to 22% of the subtest "uicheck-sw".
Could be bad-luck / noise - but maybe it is worth considering to skip that on arm?
[1]: https:/ /git.launchpad. net/~ubuntu- server/ ubuntu- helpers/ tree/cpaelzer/ check-autopkgte st-stats. sh