The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: edk2 (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This build log shows tests running for ~40s:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/e/edk2/20200807_201106_d36d2@/log.gz
This provides the evidence I was looking for in Comment #6 that the
tests can take longer
Have we tried adding edk2 source package, to "big_packages"
configuration of autopkgtest-cloud to spin up larger VM for edk2 tests
to run? I.e. a multi-core one. As the default VM is single core I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Thanks for spawning such a quality analysis out of my trivial IRC ping!
--
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 was fixed in the package edk2 - 2020.05-2ubuntu1
---
edk2 (2020.05-2ubuntu1) groovy; urgency=medium
* Increase autopkgtest timeout from 30s to 60s. LP: #1885186.
-- dann frazier Thu, 25 Jun 2020 16:17:15 -0600
** Changed in: edk2 (Ubuntu Groovy)
Status: New =>
** Description changed:
- Recently edk2 autopkgtests fail intermittently - but the frequency has
- increased quite a bit recently. The autopkgtests run QEMU to boot to an
- EFI prompt, and then power off. The run for each of the supported archs
+ edk2 autopkgtests fail intermittently - but the
The failures don't appear to follow an Ubuntu release, a host
architecture, or the guest architecture being tested. So did something
change externally? Looking at the data:
Prior to June 2020, we only saw a 2.7% failure rate (3/112).
Starting in June, that's grown to 25% (8/32). This is across
It's not clear to me what the pattern is here, so I wrote a script to
generate a csv file of the failures, including how long each test took
and which ones timed out.
** Attachment added: "edk2-autopkgtest-times.py"
And here's the resulting csv from that script.
** Attachment added: "times.csv"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1885186/+attachment/5387225/+files/times.csv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
10 matches
Mail list logo
