canonical-ubuntu-qa team mailing list archive

[Launchpad Bug Tracker <2058062@xxxxxxxxxxxxxxxxxx>]

** Merge proposal linked:
   https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462584

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058062

Title:
  amd64 workers shouldn't abort after i386 test bed failures

Status in Auto Package Testing:
  In Progress

Bug description:
  I was looking at the results of i386 tests today and noticed a pattern
  like the following:

  Mar 15 05:43:57 juju-7f2275-prod-proposed-migration-environment-2 /home/ubuntu/autopkgtest-cloud/worker/worker[3291087]: ERROR: Three tmpfails in a row, aborting worker. Log follows:
  ...
                            320s Creating nova instance adt-jammy-i386-libxml-parser-perl-20240315-051351-juju-7f2275-prod-proposed-migration-environment-2 from image adt/ubuntu-jammy-amd64-se>
                            320s autopkgtest [05:43:56]: ERROR: testbed failure: Can't resolve build dependencies on testbed

  Not being able to resolve build dependencies for i386 is a common
  occurrence and my concern here is how much time are we losing by
  aborting the worker. Is it down for 5, 10, 15 minutes until it gets
  restarted again? Any amount of downtime for this is wasteful.

  Additionally, retrying two more times is also wasteful because they
  aren't likely to get sorted.

  Finally, the ideal solution would probably involve not running tests
  where the build-deps are gonna fail at all but that seems a lot
  harder.

  I think we should look at the FAIL_STRINGS stuff here and try to
  adjust it for i386.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058062/+subscriptions