I see new runs of the patched systemd package in noble, and even though
tests-in-lxd is still failing, now the reason is not the patch failing
to apply, it's something else:

Starting autopkgtest-prepare-Rk7
4650s Created symlink /etc/systemd/system/serial-getty@getty.service → 
/dev/null.
4656s Container finished booting. Distribution Ubuntu, release noble, 
architecture amd64
4656s Running setup script 
/usr/share/autopkgtest/setup-commands/setup-testbed...
4657s sh: Attempting to set up Debian/Ubuntu apt sources automatically
4657s Failed to auto-detect apt mirror; set $MIRROR explicitly
4660s patching file /usr/bin/autopkgtest-build-lxd
4660s Creating autopkgtest-prepare-ilv
4667s 
Retrieving image: Unpack: 100% (515.00MB/s)
                                            
Retrieving image: Unpack: 100% (515.00MB/s)
                                            
Starting autopkgtest-prepare-ilv
4673s Created symlink /etc/systemd/system/serial-getty@getty.service → 
/dev/null.
4673s Created symlink /etc/systemd/system/snapd.service → /dev/null.
4673s Masking 'snapd.service', but its triggering units are still active:
4673s snapd.socket
4674s Created symlink /etc/systemd/system/snapd.seeded.service → /dev/null.
4680s Container finished booting. Distribution Ubuntu, release noble, 
architecture amd64
4680s Running setup script 
/usr/share/autopkgtest/setup-commands/setup-testbed...
4680s sh: Attempting to set up Debian/Ubuntu apt sources automatically
4680s Failed to auto-detect apt mirror; set $MIRROR explicitly
4683s Creating systemd-lxc
4690s 
Retrieving image: Unpack: 100% (1.11GB/s)
                                          
Retrieving image: Unpack: 100% (1.11GB/s)
                                          
Starting systemd-lxc
4750s running
4751s autopkgtest [05:06:03]: test tests-in-lxd: -----------------------]
4751s autopkgtest [05:06:03]: test tests-in-lxd:  - - - - - - - - - - results - 
- - - - - - - - -
4751s tests-in-lxd         FAIL non-zero exit status 1

I agree that updating systemd in jammy just for the sake of this test is
not correct. And systemd tests are so flaky, that it's possible a
migration-reference/0 run will fail as well, and then mask any
subsequent new failures. But I triggered one anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051939

Title:
  [SRU exception] backport 5.32 to Jammy and Mantic

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to