No need for such crude approach ;-)
ksekera@zglab-host-4 ~/vpp> make test-shell
...
(virtualenv) ksekera@zglab-host-4:~/vpp/test$ ./discover_tests.py
...
test_jvpp.py.TestJVpp.test_vpp_snat_callback_api
test_jvpp.py.TestJVpp.test_vpp_snat_future_api
test_dhcp.py.TestDHCP.test_dhcp6_proxy
test_dhcp
Brian,
A brute-force means of achieving your goal would be to use the "TEST="
option to run each test individually:
TEST= - filter the set of tests:
by file-name - only run tests from specified file, e.g.
TEST=test_bfd selects all tests from test_bfd.py
by file-suffix
Hi Brian,
FAILFAST=0 is the default, so there is no need to specify it.
Usually, when a test case 'runs forever', it means that the VPP crashed
while processing an API call (did you see a message about a core found
in temporary directory?), in which case python will be stuck waiting for
a lock. N
Is there a way to make:
FAILFAST=0 TIMEOUT=t make test
actually continue on to the next test if a test has reached timeout t?
The motivation is that I see at least one test case running for forever,
and I want to be able to see how many test cases are failing in total.
I didn't see that this
