Previously, unit tests were running in groups. There were technical reasons why that was the case (mostly having to do with limiting memory), but it was hard to maintain and update the autotest script.
In 18.05, limiting of memory at DPDK startup was no longer necessary, as DPDK allocates memory at runtime as needed. This has the implication that the old test grouping can now be retired and replaced with a more sensible way of running unit tests (using multiprocessing pool of workers and a queue of tests). This patchset accomplishes exactly that. This patchset conflicts with some of the earlier work on autotests [1] [2] [3], but i think it presents a cleaner solution for some of the problems highlighted by those patch series. I can integrate those patches into this series if need be. [1] http://dpdk.org/dev/patchwork/patch/40370/ [2] http://dpdk.org/dev/patchwork/patch/40371/ [3] http://dpdk.org/dev/patchwork/patch/40372/ Anatoly Burakov (7): autotest: fix printing autotest: fix invalid code on reports autotest: make autotest runner python 2/3 compliant autotest: visually separate different test categories autotest: improve filtering autotest: remove autotest grouping autotest: properly parallelize unit tests test/test/autotest.py | 13 +- test/test/autotest_data.py | 749 ++++++++++++++--------------------- test/test/autotest_runner.py | 519 ++++++++++++------------ 3 files changed, 586 insertions(+), 695 deletions(-) -- 2.17.1
