Hi David, > Hello guys, > > On Fri, Oct 22, 2021 at 3:27 PM Konstantin Ananyev > <konstantin.anan...@intel.com> wrote: > > > > link bounding auto-test internally creates emulated ethdev. > > Some tests change Rx/Tx functions of this emulated device on the fly: > > by directly modifying rte_eth_dev fields and without doing stop/start > > for these devices. > > As now ethdev uses rte_eth_fp_ops[] for fast-path functions, these > > direct changes doesn't make expected effect. > > Fix the problem by guarding fast-path functions changes with > > rte_eth_dev_stop()/rte_eth_dev_start(). > > > > Fixes: 7a0935239b9e ("ethdev: make fast-path functions to use new flat > > array") > > > > Reported-by: Lewei Yang <leweix.y...@intel.com> > > Signed-off-by: Konstantin Ananyev <konstantin.anan...@intel.com> > > I suspect there is something broken in > (bitratestats_autotest|latencystats_autotest|pdump_autotest) tests > that make use of app/test/sample_packet_forward.* code. > This code creates a portid from a ring, but I guess this port is not > properly setup wrt to API. > It goes unnoticed in CI atm, with tests returning ok. > > > Looking at main branch test in UNH, testlog.txt files are millions of > lines filled with: > > test_packet_forward() line 104: Error sending packet to port 0 > send pkts Failed > > or: > > tx_pkt_burst for not ready port > > There may be more issues, the files are just too huge. > > > Example: > https://lab.dpdk.org/results/dashboard/results/results- > uploads/test_runs/1dd418abe77644c18417dcb589e994aa/log_upload_file/2021/10/dpdk_2e437f1cd65e_2021-10-23_22-04-34_NA.zip >
Sure, I'll have a look next week. Konstantin