© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> Opened MR to blacklist TEST-15 and TEST-22
That PR on GitHub hasn't been merged yet so I think it's too soon to turn those tests off.
> ah, ok - so I did look into this, or at least some failures really similar to this, a while back, for bug 1831468.
As far as I can tell, several tests failed there because QEMU_TIMEOUT kicked in. It's different from what is going on on i386 on GitHub where the whole upstream test fails due to the global timeout.
> Let me know if that sounds familiar or if you have any debugging suggestions
Depending on where the test is run it could be 300s isn't enough for it to finish. Given that it's not particularly popular platform I assume it's run in VMs where the upstream test also launch VMs with QEMU with no acceleration whatsoever. Could you try bumping up QEMU_TIMEOUT to see whether it helps?