The initial autopkgtest results after bumping the timeout to 60s passed, but each test ran within a time length that may have passed even with the previous 30s timeout (longest case I see was 32s). Before (low- impact) SRU'ing this back, ideally we'd be able to point to a test that clearly blew passed the 30s timeout, but still eventually completed. On the other hand, waiting for such proof to appear naturally in groovy before SRU'ing back could result in more unnecessary failures. While I could be swayed either way, I think I'll wait a bit for a demonstrable case in groovy.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885186 Title: autopkgtests sometimes timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1885186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
