David Marchand <[email protected]> writes: > On Wed, Aug 23, 2023 at 5:35 PM David Marchand > <[email protected]> wrote: >> >> Integrate system-traffic.at tests as part of check-dpdk. > > CI (thinking of Intel robot) other than GHA might not be too happy > about this change. > It is hard to tell what fails in the report I received. > > A safer approach is probably to define a new check-XXX target instead > of expanding check-dpdk.
I'm not sure - at least for Intel, we can ask them to investigate. I noticed that we didn't get any new results from intel after this patch, so I wonder if this change broke something. I also noticed that without the conntrack tests (7/7) this passed, but with them, we got a failure report. Is it possible that the tests are taking too long (in which case, we need to investigate a way of optimizing this). >> >> DPDK net/tap specific logs are added to the log exclusions. >> >> Some tests that can't work with the userspace datapath are skipped by >> overriding some OVS_CHECK_* macros. >> >> ADD_VETH is implemented with a tap interface in the kernel, directly >> polled by OVS. >> >> Signed-off-by: David Marchand <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
