debcrafters-packages team mailing list archive

[Skia <2115731@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

upgrade testing code repo: https://github.com/canonical/auto-upgrade-testing
upgrade testing profiles repo: https://code.launchpad.net/auto-upgrade-testing-specifications/

Clone them both side to side, then use the following reproducer:

```
python3 -m upgrade_testing.command_line -c ../auto-upgrade-testing-specifications/profiles/ubuntu-noble-oracular-basic-amd64_qemu.yaml --provision  --adt-args='--timeout-factor=10 -d' --results-dir /tmp/upgrade_tests
```

The upgrade should fail, apparently because now autopkgtest is a bit more eager to reboot when a package needs it before running the tests, and then upgrade-testing checks right away if it's booting on the right system, which is obviously not the case.
The fix might actually be in upgrade testing code, because all that interaction between autopkgtest and that code has always been very brittle, but I wanted to track the regression in a bug anyway (SRU bug 2106167).

** Affects: autopkgtest (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: autopkgtest (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: autopkgtest (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Affects: autopkgtest (Ubuntu Oracular)
     Importance: Undecided
         Status: New

** Affects: autopkgtest (Ubuntu Plucky)
     Importance: Undecided
         Status: New

** Affects: autopkgtest (Ubuntu Questing)
     Importance: Undecided
         Status: New


** Tags: regression-update

** Also affects: autopkgtest (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: autopkgtest (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: autopkgtest (Ubuntu Plucky)
   Importance: Undecided
       Status: New

** Also affects: autopkgtest (Ubuntu Questing)
   Importance: Undecided
       Status: New

** Also affects: autopkgtest (Ubuntu Oracular)
   Importance: Undecided
       Status: New

** Description changed:

  upgrade testing code repo: https://github.com/canonical/auto-upgrade-testing
  upgrade testing profiles repo: https://code.launchpad.net/auto-upgrade-testing-specifications/
  
  Clone them both side to side, then use the following reproducer:
  
  ```
  python3 -m upgrade_testing.command_line -c ../auto-upgrade-testing-specifications/profiles/ubuntu-noble-oracular-basic-amd64_qemu.yaml --provision  --adt-args='--timeout-factor=10 -d' --results-dir /tmp/upgrade_tests
  ```
  
  The upgrade should fail, apparently because now autopkgtest is a bit more eager to reboot when a package needs it before running the tests, and then upgrade-testing checks right away if it's booting on the right system, which is obviously not the case.
- The fix might actually be in upgrade testing code, because all that interaction between autopkgtest and that code has always been very brittle, but I wanted to track the regression in a bug anyway.
+ The fix might actually be in upgrade testing code, because all that interaction between autopkgtest and that code has always been very brittle, but I wanted to track the regression in a bug anyway (SRU bug 2106167).

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2115731

Title:
  upgrade-testing is broken with autopkgtest >5.47

Status in autopkgtest package in Ubuntu:
  New
Status in autopkgtest source package in Jammy:
  New
Status in autopkgtest source package in Noble:
  New
Status in autopkgtest source package in Oracular:
  New
Status in autopkgtest source package in Plucky:
  New
Status in autopkgtest source package in Questing:
  New

Bug description:
  upgrade testing code repo: https://github.com/canonical/auto-upgrade-testing
  upgrade testing profiles repo: https://code.launchpad.net/auto-upgrade-testing-specifications/

  Clone them both side to side, then use the following reproducer:

  ```
  python3 -m upgrade_testing.command_line -c ../auto-upgrade-testing-specifications/profiles/ubuntu-noble-oracular-basic-amd64_qemu.yaml --provision  --adt-args='--timeout-factor=10 -d' --results-dir /tmp/upgrade_tests
  ```

  The upgrade should fail, apparently because now autopkgtest is a bit more eager to reboot when a package needs it before running the tests, and then upgrade-testing checks right away if it's booting on the right system, which is obviously not the case.
  The fix might actually be in upgrade testing code, because all that interaction between autopkgtest and that code has always been very brittle, but I wanted to track the regression in a bug anyway (SRU bug 2106167).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2115731/+subscriptions