On 1/12/22 17:31, David Marchand wrote: > On Wed, Jan 12, 2022 at 5:17 PM David Marchand > <[email protected]> wrote: >> >> On Wed, Jan 12, 2022 at 4:48 PM Phelan, Michael >> <[email protected]> wrote: >>> >>> Hi, >>> >>> During internal testing of the AVX-512 CI, a bug was picked up on the OVS >>> master branch which resulted in the MFEX unit tests consistently failing. I >>> believe the bug was introduced by commit >>> d446dcb7e03fc7bd4e3050c83c22233b0a46d364 “system-dpdk: Refactor common logs >>> matching”. It looks like this commit changed the logs which in turn meant >>> that the expected output became outdated causing the unit tests to fail. >>> The unit tests are still failing with the most recent updates to master so >>> this bug does not seem to have been fixed with any commits that have come >>> after the one specified. >> >> Thanks for reporting. >> I did not recheck my series after the dpdk upgrade to 21.11 (with only >> the first patch applied and the whole series does not have the issue >> since it does not rely on net/pcap anymore). >> >> Could you try the following diff: > > Sorry, forgot about gmail mangling stuff. > > Please try: https://github.com/david-marchand/ovs/commit/system-dpdk > >
Thanks for the report. And thanks, David, for checking, I can not verify the change right now, I just wanted to rant for a bit about system-dpdk testsuite being highly unstable. It depends on the system configuration too much. Today I touched my iommu configuration and now all the tests are failing due to tons of virtual address hint warnings: +2022-01-12T16:25:40.190Z|00023|dpdk|WARN|EAL: WARNING! Base virtual address hint (0x100005000 != 0x7f7855c90000) not respected! +2022-01-12T16:25:40.190Z|00024|dpdk|WARN|EAL: This may cause issues with mapping memory into secondary processes +2022-01-12T16:25:40.191Z|00025|dpdk|WARN|EAL: WARNING! Base virtual address hint (0x10000b000 != 0x7f7855e0c000) not respected! +2022-01-12T16:25:40.191Z|00026|dpdk|WARN|EAL: This may cause issues with mapping memory into secondary processes +2022-01-12T16:25:40.191Z|00027|dpdk|WARN|EAL: WARNING! Base virtual address hint (0x24000c000 != 0x7f7040000000) not respected! +2022-01-12T16:25:40.191Z|00028|dpdk|WARN|EAL: This may cause issues with mapping memory into secondary processes Maybe we should just disable all DPDK warnings? BTW, DPDK should probably not emit a warning about secondary process for applications with disabled multiprocessing. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
