One has to realize, even the good path hits the cleanup function, but entered with rc=0. It then cleans up and exits with the RC it got.
The bad case OTOH seems to do parts of the cleanup function, but not all of it. It ends the tests, with more successful tests (151) but then enters cleanup with a bad RC. Note: There is also an autopkgtest/nova issue in the bad log: 5063s /home/ubuntu/autopkgtest/ssh-setup/nova: 234: [: x86_64: unexpected operator 5063s /home/ubuntu/autopkgtest/ssh-setup/nova: 237: [: x86_64: unexpected operator But myself and bryce think this is an orthogonal issue. Diving into the log a bit deeper made me find: 4: OVS-DPDK - ping vhost-user ports FAILED (system-dpdk.at:148) 5: OVS-DPDK - ping vhost-user-client ports FAILED (system-dpdk.at:224) 16: OVS-DPDK - MTU increase vport port FAILED (system-dpdk.at:609) 17: OVS-DPDK - MTU decrease vport port FAILED (system-dpdk.at:651) 20: OVS-DPDK - MTU upper bound vport port FAILED (system-dpdk.at:767) 21: OVS-DPDK - MTU lower bound vport port FAILED (system-dpdk.at:809) The partial confusion is from the test running multiple suites: => openvswitch-afxdp-testsuite Good 136 skip 39 => system-dpdk-testsuite Good 142 skip 49 Fail 6 => system-userspace-testsuite Good 151 skip 36 => system-offloads-testsuite Good 152 skip 33 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067889 Title: DPDK 23.11.1 / OVS 3.3.0 cause test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2067889/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
