[v2,00/10] Make unit tests great again

Message ID 1531498808-21940-1-git-send-email-reshma.pattan@intel.com (mailing list archive)


Pattan, Reshma July 13, 2018, 4:19 p.m. UTC
  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 merges changes done in [1], [2] and [3]

[1] http://dpdk.org/dev/patchwork/patch/40370/
[2] http://dpdk.org/dev/patchwork/patch/40371/
[3] http://patches.dpdk.org/patch/40373/

v2: merged changes done in patch set [1],[2] and [3]
and created patches 08/10, 09/10, 10/10

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

Jananee Parthasarathy (1):
  mk: update make targets for classified testcases

Reshma Pattan (2):
  autotest: add new test cases to autotest
  autotest: update result for skipped test cases

 mk/rte.sdkroot.mk                |    4 +-
 mk/rte.sdktest.mk                |   33 +-
 test/test/autotest.py            |   13 +-
 test/test/autotest_data.py       | 1101 +++++++++++++++++++++++---------------
 test/test/autotest_runner.py     |  519 +++++++++---------
 test/test/autotest_test_funcs.py |    6 +-
 6 files changed, 972 insertions(+), 704 deletions(-)