From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/2] CI: switch to the new runner
Date: Wed, 13 Jul 2022 13:20:04 +0200 [thread overview]
Message-ID: <20220713132004.5bcf3910@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220712173237.23949-2-amikan@ilbers.de>
Am Tue, 12 Jul 2022 20:32:36 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> Switch CI from legacy runner removed in Avocado 97.0 to the nrunner.
> To make it run serialized limit maximum task count to 1.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> scripts/ci_build.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/ci_build.sh b/scripts/ci_build.sh
> index b1ec691..fa7208c 100755
> --- a/scripts/ci_build.sh
> +++ b/scripts/ci_build.sh
> @@ -143,5 +143,5 @@ export VIRTUAL_ENV="./"
> set -x
>
> avocado $VERBOSE run "$TESTSUITE_DIR/citest.py" \
> - -t $TAGS --test-runner=runner --disable-sysinfo \
> + -t $TAGS --nrunner-max-parallel-tasks=1 --disable-sysinfo \
Why 1 and not 42 or nproc? Because our tests are written in a way that
they build onto each other, so we lack modularization and are pretty
much still on a monolith like back in the shell age?
Henning
> -p quiet=$QUIET -p cross=$CROSS_BUILD -p time_to_wait=$TIMEOUT
next prev parent reply other threads:[~2022-07-13 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:32 [PATCH 0/2] Adopt CI to Avocado 97.0 Anton Mikanovich
2022-07-12 17:32 ` [PATCH 1/2] CI: switch to the new runner Anton Mikanovich
2022-07-13 11:20 ` Henning Schild [this message]
2022-07-13 12:08 ` Anton Mikanovich
2022-07-12 17:32 ` [PATCH 2/2] Revert "scripts/ci_build.sh: Set avocado-framework version to 96.0" Anton Mikanovich
2022-07-13 5:19 ` Jan Kiszka
2022-07-13 13:12 ` Gylstorff Quirin
2022-07-13 13:21 ` Anton Mikanovich
2022-07-14 9:19 ` Jan Kiszka
2022-07-14 12:50 ` Henning Schild
2022-07-20 5:52 ` [PATCH 0/2] Adopt CI to Avocado 97.0 Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220713132004.5bcf3910@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox