On 25/02/2022 22.01, Cleber Rosa wrote:
Even though there have been a number of improvements (and some pretty deep internal changes) since Avocado 88.1, only one change should affect "make check-avocado".With the nrunner architecture, test execution happens in parallel by default. But, tests may fail due to insufficient timeouts or similar reasons when run under systems with limited or shared resources. To avoid breakages, especially on CI, let's keep the serial execution until proven that it won't impact the CI jobs. Signed-off-by: Cleber Rosa <cr...@redhat.com> --- tests/Makefile.include | 1 + tests/requirements.txt | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/tests/Makefile.include b/tests/Makefile.include index e7153c8e91..676aa0d944 100644 --- a/tests/Makefile.include +++ b/tests/Makefile.include @@ -135,6 +135,7 @@ check-avocado: check-venv $(TESTS_RESULTS_DIR) get-vm-images $(if $(AVOCADO_TAGS),, --filter-by-tags-include-empty \ --filter-by-tags-include-empty-key) \ $(AVOCADO_CMDLINE_TAGS) \ + --nrunner-max-parallel-tasks=1 \
Could you maybe change it so that it uses the "-jX" setting from "make" instead? ... that way the users could decide whether they want to run the tests in parallel or not.
I think you could get that value from the MAKEFLAGS env variable, see tests/check-block.sh :
JOBS=$(echo "$MAKEFLAGS" | sed -n 's/\(^\|.* \)-j\([0-9]\+\)\( .*\|$\)/-j \2/p') Thomas
