From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 05/15] CI: move to avocado to 99.0
Date: Wed, 25 Jan 2023 08:10:15 +0100 [thread overview]
Message-ID: <20230125081015.189540f0@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230124204558.31025-6-amikan@ilbers.de>
Am Tue, 24 Jan 2023 22:45:48 +0200
schrieb Anton Mikanovich <amikan@ilbers.de>:
> From: Henning Schild <henning.schild@siemens.com>
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> 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 fa7208c..84a3e47 100755
> --- a/scripts/ci_build.sh
> +++ b/scripts/ci_build.sh
> @@ -21,7 +21,7 @@ if ! command -v avocado > /dev/null; then
> rm -rf /tmp/avocado_venv
> virtualenv --python python3 /tmp/avocado_venv
> source /tmp/avocado_venv/bin/activate
> - pip install avocado-framework==96.0
> + pip install avocado-framework==99.0
100.1 in the meantime, or we maybe step back to 92.0 LTS
Not sure, we can also take that 99.
Henning
> fi
>
> # Get Avocado build tests path
next prev parent reply other threads:[~2023-01-25 7:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:45 [PATCH v2 00/15] Add developers test Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 01/15] CI: Enable downloads dir sharing Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 02/15] CI: Add IMAGE_INSTALL override Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 03/15] CI: Add developers test Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 04/15] CI: Remove duplicated targets Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 05/15] CI: move to avocado to 99.0 Anton Mikanovich
2023-01-25 7:10 ` Henning Schild [this message]
2023-01-25 7:42 ` Anton Mikanovich
2023-01-25 11:39 ` Henning Schild
2023-01-24 20:45 ` [PATCH v2 06/15] CI: fix shell coding style Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 07/15] CI: install qemu-system when qemu testing is requested Anton Mikanovich
2023-01-25 8:18 ` Henning Schild
2023-01-24 20:45 ` [PATCH v2 08/15] testsuite: remove tests from "fast" set Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 09/15] CI: Get rid of setting cross from outside Anton Mikanovich
2023-01-25 8:22 ` Henning Schild
2023-01-24 20:45 ` [PATCH v2 10/15] CI: Make cross compile to be default Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 11/15] CI: Get rid of setting repro from outside Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 12/15] CI: Allow example module checking disabling Anton Mikanovich
2023-01-25 8:29 ` Henning Schild
2023-01-24 20:45 ` [PATCH v2 13/15] testsuite: Fix terminal broken after run test executed Anton Mikanovich
2023-01-24 20:45 ` [PATCH v2 14/15] CI: Update testsuite documentation Anton Mikanovich
2023-01-25 8:31 ` Henning Schild
2023-01-24 20:45 ` [PATCH v2 15/15] CI: Add single target test case 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=20230125081015.189540f0@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