Comment 11 for bug 1785262
Revision history for this message
| Heather Ellsworth (hellsworth) wrote | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
After some more investigation, here are the main points that make this issue a tricky one to debug:
1. The test failure is not isolated. While the uicheck-sw test is the culprit, it is just an umbrella for many other tests. And it's those smaller tests that the failure occurs all over. This makes it hard to just "fix the tests".
2. I have not been able to reproduce this locally on a rpi4. Laney pointed out that perhaps having multiple containers running the same test might generate the load needed (assuming that plays a key role in the failures seen on LP) and I'll certainly give this a shot.
3. Currently if you look at the recent hirsute armhf and arm64 LO test results, you'll see that the rate of failure is way down (about 1/10 times). But just a couple of weeks ago the failure rate was much higher. This suggests that it's load on the nodes causing the problem because that's when the infra was quite busy.
4. Marking the test simply as "flaky" won't work because it's actually autopkgtest killing the process
The approach going forward is to try and be clever about letting this uicheck-sw test timeout and not be considered a failure:
https:/
A test build on both armhf and arm64 to try out these changes:
https:/