Am 18.08.19 um 17:18 schrieb Michael Biebl: > Am 17.08.19 um 21:23 schrieb Paul Gevers: >> Source: network-manager, systemd >> Control: found -1 network-manager/1.20.0-1 >> Control: found -1 network-manager/1.19.90-2 >> Control: found -1 systemd/241-7 >> Severity: serious >> X-Debbugs-CC: debian...@lists.debian.org >> User: debian...@lists.debian.org >> Usertags: breaks needs-update >> >> Dear maintainers, >> >> With a recent upload of network-manager the autopkgtest of systemd fails >> in testing when that autopkgtest is run with the binary packages of >> network-manager from unstable. It passes when run with only packages >> from testing. In tabular form: >> pass fail >> network-manager from testing 1.20.0-1 >> systemd from testing 241-7 >> versioned deps [0] from testing from unstable >> all others from testing from testing >> >> I copied some of the output at the bottom of this report. (It doesn't >> show anything that isn't there in a successful run, normally it continues). >> >> Currently this regression is blocking the migration of network-manager >> to testing [1]. Due to the nature of this issue, I filed this bug report >> against both packages. Can you please investigate the situation and >> reassign the bug to the right package? >> >> More information about this bug and the reason for filing it can be found on >> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation >> >> Paul >> >> [0] You can see what packages were added from the second line of the log >> file quoted below. The migration software adds source package from >> unstable to the list if they are needed to install packages from >> network-manager/1.20.0-1. I.e. due to versioned dependencies or >> breaks/conflicts. >> [1] https://qa.debian.org/excuses.php?package=network-manager >> >> https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/2754701/log.gz >> >> autopkgtest [12:20:19]: test boot-smoke: [----------------------- >> reboot #0 >> bash: line 1: 6405 Killed >> /tmp/autopkgtest-lxc.d0a1dm24/downtmp/build.Yzc/src/debian/tests/boot-smoke >> 2> >(tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stderr >&2) >>>> (tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stdout) >> autopkgtest [12:20:20]: test process requested reboot with marker 1 >> checking for failed unmounts for user systemd >> checking for connection timeouts >> checking that polkitd runs >> autopkgtest [12:20:31]: test boot-smoke: -----------------------] >> > > I've created an LXC container via > autopkgtest-build-lxc debian bullseye > and got the same autopkgtest failure using this container. > So this looks like a regression that was introduced outside of > systemd/network-manager > > I've also tried a qemu backed autopkgtest run and there the tests > completed successfully. > Might this be a regression introduced by LXC itself (and or in > combination with a newer kernel?)
My test system is running unstable, i.e. I was using lxc_1:3.1.0+really3.0.4-1 After downgrading lxc to 1:3.1.0+really3.0.3-8, boot-smoke did successfully pass again. Paul, which lxc version was used to run the autopkgtest tests? Is it possible to get access to a system with the exact same configuration as on ci.debian.net so one can interactively debug this issue? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature