tests: "force solo" testcase support 86/28586/8
authorAndrew Yourtchenko <ayourtch@gmail.com>
Wed, 26 Aug 2020 14:33:54 +0000 (14:33 +0000)
committerOle Trøan <otroan@employees.org>
Thu, 27 Aug 2020 08:03:38 +0000 (08:03 +0000)
commita3b7c554c669afc627f9a1e32666211bb6fb6b25
tree625a8fd262f823d0bd79ec779430a6df905368df
parentd135487aff499b3450fd8d3013b6af52d80e96a1
tests: "force solo" testcase support

Some of the tests are time-sensitive, and at present require a non-trivial
modification in order to run at high concurrency.

Without these modifications, they intermittently fail, and require
the test retries.

Rather than setting them to the extended tests and forgetting
about them, put them into a "solo" set, which gets run in a
single-threaded mode after the rest of the tests are done.

Mark a few of the tests that showed errors during TEST_JOBS=48
as forced-solo.

Also, give a better diagnostic if the testcase misses a docstring
needed to represent it in the diagnostic outputs.

Type: fix

Change-Id: I33fe62eb17edc1885bd2c3523892051d52da6546
Signed-off-by: Andrew Yourtchenko <ayourtch@gmail.com>
src/plugins/dhcp/test/test_dhcp.py
src/plugins/dhcp/test/test_dhcp6.py
src/plugins/flowprobe/test/test_flowprobe.py
src/plugins/memif/test/test_memif.py
test/framework.py
test/run_tests.py
test/test_bfd.py
test/test_ip6.py
test/test_session.py
test/test_util.py