This ordering is interesting (from a good case): $ grep -e 'autopkgtest .*\[.*\]: test .*:' -e get_netfilter_capabilities old-iptables-good.txt test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ... ok test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ... ok autopkgtest [20:42:36]: test test-ufw.py: preparing testbed autopkgtest [20:44:18]: test test-ufw.py: [----------------------- autopkgtest [20:44:22]: test test-ufw.py: -----------------------] autopkgtest [20:44:22]: test test-ufw.py: - - - - - - - - - - results - - - - - - - - - - autopkgtest [20:44:22]: test root-unittest: preparing testbed autopkgtest [20:46:24]: test root-unittest: [----------------------- autopkgtest [20:52:16]: test root-unittest: -----------------------] autopkgtest [20:52:16]: test root-unittest: - - - - - - - - - - results - - - - - - - - - - autopkgtest [20:52:16]: test unittest: preparing testbed autopkgtest [20:52:24]: test unittest: [----------------------- test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ... ok autopkgtest [20:59:10]: test unittest: -----------------------] autopkgtest [20:59:11]: test unittest: - - - - - - - - - - results - - - - - - - - - -
That means at least the first two of the times the test runs seems to be from the build as two of the autopkgtest entries come with "build-needed". That is interesting as: 1. the new ufw's actual build was obviously against proposed and there things worked fine You can see both occasions of the test in the build log at [1] 2. that build ran on all my tests before upload and it worked fine there Two occasions in http://paste.ubuntu.com/p/RKFvhTP8Ft/ 3. it is not the test, but the prep stage for "build-needed" that is failing which might also be the reason why there is no auto-timeout-abort The bad part, in a local build this just works fine: - autopkgtest in a VM is ok - sbuild building the package itself is ok Next steps: - what does this particular test actually do that could hang - what might be different in that build time comapred to "local-autopkgtest-vm" and the "normal LP builds" [1]: https://launchpadlibrarian.net/437577267/buildlog_ubuntu-eoan- amd64.ufw_0.36-1ubuntu2_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1840633/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
