I've reworked the patches using gbp and run the 'scenarios' autopkgtest for each series. The tests pass for all but Jammy; not clear why we have a missing builddep:
``` Program pytest-3 pytest3 found: NO ../meson.build:28:0: ERROR: Program 'pytest-3 pytest3' not found or not executable ``` It may be environment-specific although I don't think my env is particularly special. Removing `<!nocheck>` from the python dependencies in d/control allows the tests to pass (see attached diff). I also saw some failures of test_netplan_try_lp2083029 in Jammy; looks like networkd being very slow. My environment is heavily IO-contested nested virt at the moment so I expect that this isn't something to worry about; extending `timeout` in `try_and_settle` lets the test pass. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083029 Title: Try does not recover network To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2083029/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
