Hide Forgot
Description of problem: When running network tests and got an error: hwcert-backend run --test network --device em1 Error: No such test "network" Version-Release number of selected component (if applicable): hwcert-client-1.7.0-20131203.el7.noarch
That's because there is no such test - we've replaced the old network test with rate-specific tests: 100MegEthernet, 1GigEthernet, and 10GigEthernet. You can run them via the --tag option: > hwcert-backend run --tag network You can also run the test for em1 using the --device option by itself: > hwcert-backend run --device em1
network still exists as a target? This is for some IB otherwise they would need to run *Ethernet? however it nust be planned bofore ir can be run. [root@unused ~]# hwcert-backend run --test network --device eth0 Error: No such test "network" [root@unused ~]# hwcert-backend plan --add --test network --device eth0 Added test [root@unused ~]# hwcert-backend print Test Plan: ---------------------------------------------------------------- suspend device:08/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 USB3 pci0000:00/0000:00:1c.6/0000:0e:00.0/usb4 USB2 pci0000:00/0000:00:1a.0/usb1 ... Ethernet eth0 pci0000:00/0000:00:19.0/net/eth0 network eth0 net_f0_de_f1_63_7e_71 memory ... hwcert-backend run --test network Running the following tests: suspend device:08/PNP0C09:00/PNP0C0A:00/power_supply/BAT0 network eth0 net_f0_de_f1_63_7e_71 info
(In reply to Rob Landry from comment #2) > network still exists as a target? This is for some IB otherwise they would > need to run *Ethernet? however it nust be planned bofore ir can be run. > Yes, this works. I was assuming this was a case where other network interfaces were in the test plan. The "network" test runs without rate requirements.
(In reply to Greg Nichols from comment #1) > That's because there is no such test - we've replaced the old network test > with rate-specific tests: 100MegEthernet, 1GigEthernet, and 10GigEthernet. > > You can run them via the --tag option: > > > hwcert-backend run --tag network > > You can also run the test for em1 using the --device option by itself: > > > hwcert-backend run --device em1 As the network test is not exist anymore, is it necessary to add a prompt or something else when user want to run it ?
(In reply to Dong Zhu from comment #4) > (In reply to Greg Nichols from comment #1) > > That's because there is no such test - we've replaced the old network test > > with rate-specific tests: 100MegEthernet, 1GigEthernet, and 10GigEthernet. > > > > You can run them via the --tag option: > > > > > hwcert-backend run --tag network > > > > You can also run the test for em1 using the --device option by itself: > > > > > hwcert-backend run --device em1 > > As the network test is not exist anymore, is it necessary to add a prompt or > something else when user want to run it ? See comment #2
(In reply to Rob Landry from comment #5) > (In reply to Dong Zhu from comment #4) > > (In reply to Greg Nichols from comment #1) > > > That's because there is no such test - we've replaced the old network test > > > with rate-specific tests: 100MegEthernet, 1GigEthernet, and 10GigEthernet. > > > > > > You can run them via the --tag option: > > > > > > > hwcert-backend run --tag network > > > > > > You can also run the test for em1 using the --device option by itself: > > > > > > > hwcert-backend run --device em1 > > > > As the network test is not exist anymore, is it necessary to add a prompt or > > something else when user want to run it ? > > See comment #2 Yes, It would work, acutally perhaps it's kinda confusing for users.