From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v12 00/16] Update Avocado testsuite
Date: Mon, 27 Sep 2021 14:31:34 +0300 [thread overview]
Message-ID: <ba578954-9b94-8d1d-1d29-308811e8f85d@ilbers.de> (raw)
In-Reply-To: <20210924141850.6cf5d6fd@md1za8fc.ad001.siemens.net>
On 24.09.21 15:18, Henning Schild wrote:
> Am Fri, 17 Sep 2021 20:00:17 +0300
> schrieb Anton Mikanovich <amikan@ilbers.de>:
>
>> This patchset provides implementation of build and vm_start tests
>> functionality in Python with help of Avocado framework.
>> Scripts ci_build and vm_smoke_test are rewritten to call Avocado.
>> ci_build and vm_smoke_test are left for compatibility and
>> should be replaced by direct avocado calls later.
> What to stay compatible with? I think the old one should be dropped
> right when the new one comes. Or do we maintain both wile we have both?
> I am all for dropping the old and merging this rather soon. Because any
> change made is likely to add tests ... and will have merge conflicts
> with this not being in the tree yet.
>
> Henning
I'm ok to remove old shell code, nobody would like to maintain both.
Just send v13 without it and hope to merge the patchset in next days.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2021-09-27 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 17:00 Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 01/16] start_vm.py: Fix target name handling Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 02/16] start_vm.py: Add output and PID file vm_start.py options Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 03/16] start_vm.py: Add MIPS support Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 04/16] start_vm.py: Fix ubuntu image name Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 05/16] vm_boot_test: Fix log file path in vm_boot_test Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 06/16] vm_boot_test: Remove external varianter Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 07/16] vm_boot_test: Improve QEMU images checking Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 08/16] build_test: Refactoring build tests cases Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 09/16] testsuite: Add Python generations for testsuite in gitignore Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 10/16] testsuite: Fix test suite prepare guide Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 11/16] gitlab-ci: Add Avocado build artifacts Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 12/16] gitlab-ci: Add debug flag Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 13/16] vm_boot_test: Add automatic bitbake init Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 14/16] build_test: Protect ubuntu target with KFAIL Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 15/16] ci_build: Migrate to Avocado Anton Mikanovich
2021-09-17 17:00 ` [PATCH v12 16/16] vm_smoke_test: " Anton Mikanovich
2021-09-24 12:18 ` [PATCH v12 00/16] Update Avocado testsuite Henning Schild
2021-09-27 11:31 ` Anton Mikanovich [this message]
2021-09-30 16:48 ` 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=ba578954-9b94-8d1d-1d29-308811e8f85d@ilbers.de \
--to=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--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