Hello Stephen, I noticed a (time based?) failure of the pcapng unit test in some UNH Debian 11 container. Please have a look.
https://lab.dpdk.org/results/dashboard/patchsets/29604/ ----------------------------------- stdout ----------------------------------- RTE>>pcapng_autotest + ------------------------------------------------------- + + Test Suite : Test Pcapng Unit Test Suite + ------------------------------------------------------- + pcapng: output file /tmp/pcapng_test_oIueHb.pcapng + TestCase [ 0] : test_add_interface succeeded pcapng: output file /tmp/pcapng_test_4hbuWV.pcapng 16:51:22.955616600: EE:47:6C:93:DE:F0 -> FF:FF:FF:FF:FF:FF type 800 length 200 + TestCase [ 1] : test_write_packets failed + ------------------------------------------------------- + + Test Suite Summary : Test Pcapng Unit Test Suite + ------------------------------------------------------- + + Tests Total : 2 + Tests Skipped : 0 + Tests Executed : 2 + Tests Unsupported: 0 + Tests Passed : 1 + Tests Failed : 1 + ------------------------------------------------------- + Test Failed RTE>> ----------------------------------- stderr ----------------------------------- EAL: Detected CPU lcores: 16 EAL: Detected NUMA nodes: 2 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized EAL: Device 0000:03:00.0 is not NUMA-aware APP: HPET is not enabled, using TSC as default timer Timestamp out of range [16:51:16.481074161 .. 16:51:22.953203736] pcap_dispatch: failed: -- David Marchand
