public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v14 00/16] Update Avocado testsuite
Date: Thu, 21 Oct 2021 11:48:36 +0200	[thread overview]
Message-ID: <20211021094836.GG27644@yssyq.m.ilbers.de> (raw)
In-Reply-To: <dd2e18df-f197-5fd9-6846-23662ca76d9b@siemens.com>

On Thu, Oct 14, 2021 at 05:51:22PM +0200, Jan Kiszka wrote:
> > In a nutshell, the execution environment can have the control how the necessary
> > tools are provided (Debian packages or pip), just as it is today with the other
> > packages required by Isar.
> 
> You broke gitlab-ci, please fix. This can only reasonably be done in
> Isar, not outside (avokado is not build dependency, this is not part of
> kas-isar).

We can do this to unblock the situation. However, I think that drawing the line
between build dependency and test tooling is a disservice for kas users. One of
the goals for migrating to a test framework is to split the previously
monolithic testsuite into individual testcases and the ability to run them
manually.

People like kas because it hides the environment preparation issues while also
providing the necessary customization options. If a user spawns a kas shell to
make his changes, he could use e.g. avocado run
testsuite/build_test/build_test.py -t sdk to test only the area he is
interested in. The same for debugging failing CI cases without having to run
the full testsuite, which meanwhile takes several hours.

That is why I think providing the test tooling in the default image is actually
a good thing for the developers.

With kind regards,
Baurzhan.

  parent reply	other threads:[~2021-10-21  9:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 16:45 Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 01/16] start_vm.py: Fix target name handling Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 02/16] start_vm.py: Add output and PID file vm_start.py options Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 03/16] start_vm.py: Add MIPS support Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 04/16] start_vm.py: Fix ubuntu image name Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 05/16] vm_boot_test: Fix log file path in vm_boot_test Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 06/16] vm_boot_test: Remove external varianter Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 07/16] vm_boot_test: Improve QEMU images checking Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 08/16] build_test: Refactoring build tests cases Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 09/16] testsuite: Add Python generations for testsuite in gitignore Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 10/16] testsuite: Fix test suite prepare guide Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 11/16] gitlab-ci: Add Avocado build artifacts Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 12/16] gitlab-ci: Add debug flag Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 13/16] vm_boot_test: Add automatic bitbake init Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 14/16] build_test: Protect ubuntu target with KFAIL Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 15/16] ci_build: Migrate to Avocado Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 16/16] vm_smoke_test: " Anton Mikanovich
2021-10-14  8:54 ` [PATCH v14 00/16] Update Avocado testsuite Jan Kiszka
2021-10-14 10:25   ` Baurzhan Ismagulov
2021-10-14 15:51     ` Jan Kiszka
2021-10-19  8:34       ` Schmidt, Adriaan
2021-10-22  6:54         ` Anton Mikanovich
2021-10-19  9:54       ` Henning Schild
2021-10-21  9:48       ` Baurzhan Ismagulov [this message]
     [not found] <1633020197-26007-1-git-send-email-anton.mikanovich@promwad.com>
2021-10-13 14:06 ` 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=20211021094836.GG27644@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --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