> Hi All, > I want to test some changes done for OVS-DPDK. > I am able to run make check-dpdk , but I guess that is enough as I see that > test may not exercise the code path that I have changed. > On reading Testing - Open vSwitch 2.17.90 > documentation<https://docs.openvswitch.org/en/latest/topics/testing/>, I get > a feeling I can get userspace netdev tested by running "make > check-system-userspace" > > I am running this on my development machine, I think Vagrant with centos was > complaining the same. > > This is what I see in the logs when I run > "make check-system-userspace TESTSUITEFLAGS='-k datapath' TESTSUITEFLAGS='1'" > > > Log file: > ========= > ## ---------------------- ## > ## Detailed failed tests. ## > ## ---------------------- ## > > # -*- compilation -*- > 1. system-traffic.at:3: testing datapath - ping between two ports ... > system-traffic.at:4: waiting while ip link show ovs-netdev... > Device "ovs-netdev" does not exist. > system-traffic.at:4: wait succeeded immediately > ./system-traffic.at:4: ovsdb-tool create conf.db > $abs_top_srcdir/vswitchd/vswitch.ovsschema > ./system-traffic.at:4: ovsdb-server --detach --no-chdir --pidfile --log-file > --remote=punix:$OVS_RUNDIR/db.sock > stderr: > 2022-02-11T23:53:35Z|00001|vlog|INFO|opened log file > /usr/src/ovs/tests/system-userspace-testsuite.dir/001/ovsdb-server.log > ./system-traffic.at:4: sed < stderr ' > /vlog|INFO|opened log file/d > /ovsdb_server|INFO|ovsdb-server (Open vSwitch)/d' > ./system-traffic.at:4: ovs-vsctl --no-wait init > ./system-traffic.at:4: ovs-vswitchd --disable-system --detach --no-chdir > --pidfile --log-file -vvconn -vofproto_dpif -vunixctl > stderr: > 2022-02-11T23:53:35Z|00001|vlog|INFO|opened log file > /usr/src/ovs/tests/system-userspace-testsuite.dir/001/ovs-vswitchd.log > 2022-02-11T23:53:35Z|00002|ovs_numa|INFO|Discovered 16 CPU cores on NUMA node > 0 > 2022-02-11T23:53:35Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 16 CPU > cores > 2022-02-11T23:53:35Z|00004|reconnect|INFO|unix:/usr/src/ovs/tests/system-userspace-testsuite.dir/001/db.sock: > connecting... > 2022-02-11T23:53:35Z|00005|reconnect|INFO|unix:/usr/src/ovs/tests/system-userspace-testsuite.dir/001/db.sock: > connected > 2022-02-11T23:53:35Z|00006|dpdk|INFO|DPDK Disabled - Use > other_config:dpdk-init to enable > 2022-02-11T23:53:35Z|00007|dpif_netlink|INFO|The kernel module does not > support meters. > ./system-traffic.at:4: sed < stderr ' > /ovs_numa|INFO|Discovered /d > /vlog|INFO|opened log file/d > /vswitchd|INFO|ovs-vswitchd (Open vSwitch)/d > /reconnect|INFO|/d > /dpif_netlink|INFO|Generic Netlink family .ovs_datapath. does not exist/d > /ofproto|INFO|using datapath ID/d > /netdev_linux|INFO|.*device has unknown hardware address family/d > /ofproto|INFO|datapath ID changed to fedcba9876543210/d > /dpdk|INFO|DPDK Disabled - Use other_config:dpdk-init to enable/d > /netlink_socket|INFO|netlink: could not enable listening to all nsid/d > /probe tc:/d > /tc: Using policy/d' > --- /dev/null 2022-02-08 12:38:20.944991451 -0800 > +++ /usr/src/ovs/tests/system-userspace-testsuite.dir/at-groups/1/stdout > 2022-02-11 15:53:35.455808528 -0800 > @@ -0,0 +1 @@ > +2022-02-11T23:53:35Z|00007|dpif_netlink|INFO|The kernel module does not > support meters. > ovsdb-server.log: >> 2022-02-11T23:53:35.384Z|00001|vlog|INFO|opened log file >> /usr/src/ovs/tests/system-userspace-testsuite.dir/001/ovsdb-server.log >> 2022-02-11T23:53:35.396Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) >> 2.16.2 > ovs-vswitchd.log: >> 2022-02-11T23:53:35.422Z|00001|vlog|INFO|opened log file >> /usr/src/ovs/tests/system-userspace-testsuite.dir/001/ovs-vswitchd.log >> 2022-02-11T23:53:35.426Z|00002|ovs_numa|INFO|Discovered 16 CPU cores on NUMA >> node 0 >> 2022-02-11T23:53:35.426Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 16 >> CPU cores >> 2022-02-11T23:53:35.426Z|00004|reconnect|INFO|unix:/usr/src/ovs/tests/system-userspace-testsuite.dir/001/db.sock: >> connecting... >> 2022-02-11T23:53:35.426Z|00005|reconnect|INFO|unix:/usr/src/ovs/tests/system-userspace-testsuite.dir/001/db.sock: >> connected >> 2022-02-11T23:53:35.430Z|00006|dpdk|INFO|DPDK Disabled - Use >> other_config:dpdk-init to enable >> 2022-02-11T23:53:35.434Z|00007|dpif_netlink|INFO|The kernel module does not >> support meters. >> 2022-02-11T23:53:35.441Z|00008|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.16.2 > 1. system-traffic.at:3: 1. datapath - ping between two ports > (system-traffic.at:3): FAILED (system-traffic.at:4) > > I noticed that when the test was running, I really don't see the ovs-netdev > interface, is that the reason why it fails?
It fails because it finds unexpected log message in the stderr. Apparently, you're running a fairly old kernel that doesn't have support for meters. > if so, can someone please let me know how to fix this and run unit tests for > DPDK/Userspace? You may either upgrade your kernel to 4.15+ or simply add the warning to the ignore list: diff --git a/tests/ofproto-macros.at b/tests/ofproto-macros.at index 736d9809c..9233aa468 100644 --- a/tests/ofproto-macros.at +++ b/tests/ofproto-macros.at @@ -174,6 +174,7 @@ m4_define([_OVS_VSWITCHD_START], /ofproto|INFO|datapath ID changed to fedcba9876543210/d /dpdk|INFO|DPDK Disabled - Use other_config:dpdk-init to enable/d /netlink_socket|INFO|netlink: could not enable listening to all nsid/d +/dpif_netlink|INFO|The kernel module does not support meters./d /probe tc:/d /tc: Using policy/d']]) ]) --- Best regards, Ilya Maximets. _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
