There are a lot of tmpfail test failures; more than usual. Just spot checking but a portion seem to match the errors from this bug report's log file, e.g.:
In general, it seems that retriggering the tests once has been enough to get them to pass, but it's a bit labor intensive. If the tmpfails are indeed due to VM infrastructure issues it would be beneficial to get some analysis under way.
There are a lot of tmpfail test failures; more than usual. Just spot checking but a portion seem to match the errors from this bug report's log file, e.g.:
# https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- oracular/ oracular/ s390x/p/ pythran/ 20240531_ 093453_ cc6d6@/ log.gz
693s No UUID given. Instance won't be deleted!
693s <VirtSubproc>: failure: setup script failed with code 1...
693s autopkgtest [09:34:52]: ERROR: testbed failure: unexpected eof from the testbed
Other tmpfails have different error messages, bit I suspect may be same root cause:
# https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- oracular/ oracular/ armhf/r/ rust-bytecheck/ 20240531_ 101049_ 0a27a@/ log.gz
340s autopkgtest [10:10:49]: ERROR: testbed failure: timed out on command "sh -ec #!/bin/sh
In general, it seems that retriggering the tests once has been enough to get them to pass, but it's a bit labor intensive. If the tmpfails are indeed due to VM infrastructure issues it would be beneficial to get some analysis under way.