- Attended sprint sessions (today, rest of the week)
- Worked a lot more on impish opening, deployed the new autopkgtest (see many past status updates) and switched everything over to that. Quite a few followups were required but we’re more or less stable now.
- The archive is open now for uploads.
- but we’ve got a big arm64 backlog. There are a few issues there
- A possible cloud misconfiguration (in our user’s quotas) is causing spawns to fail sometimes. I’ve got a ticket with Canonical IS to get that fixed, so that will hopefully stop soon.
- Instances are often failng to reboot, could be a bug in the kernel or edk2. This means that packages which include many autopkgtests - a lot of rebooting - have a higher chance of failing like this. When that happens we requeue the test, but it might happen again multiple times. That’s affecting throughput somewhat. The kernel team is looking into it for us, hopefully we’ll have a resolution soon.
- The links between the cloud where we request / process test results and the one where the tests are actually run went down multiple times on Friday, over the weekend and today (Monday). When that happens, the network connection is broken and autopkgtest fails the test run. It needs to be restarted then, which can set long running tests back a long way.
- but we’ve got a big arm64 backlog. There are a few issues there
5 Likes