public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
	"ubely@ilbers.de" <ubely@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/4] Basic hardware testing support
Date: Wed, 24 May 2023 06:30:10 +0200	[thread overview]
Message-ID: <01510fd6fb6722d661b7d23e6e3ba4f89440498f.camel@siemens.com> (raw)
In-Reply-To: <06fd09e60c6af243f836bc06736b05218734e9d3.camel@siemens.com>

On Wed, 2023-05-24 at 03:06 +0000, 'MOESSBAUER, Felix' via isar-users
wrote:
> On Wed, 2023-05-24 at 04:45 +0200, Uladzimir Bely wrote:
> > Isar is currently able to run tests only on qemu targets over SSH.
> > 
> > This patchset adds basic support of running tests on real hardware
> > targets in similar way. There are the following limitations:
> > 
> > - User `ci` should be pre-configured (e.g., isar-ci-ssh-setup recipe
> > used when generating the image), similar to qemu testing;
> > - The image should be flashed on the board before running tests;
> > - The target should be turned on and accessible over SSH;
> > 
> > Possible ways to improve this:
> > - Support turning on/off the hardware (via USB switches or similar);
> > - Automation of board software update.
> 
> The flashing and powerctl features are implemented in MTDA [1]. We also
> use that in a lab for CI tests of ISAR images on hardware devices.

I would say flashing is not necessary or at least no hard requirement.
We have LAVA (tool behind kernelci) setups deployed that implement NFS
based booting of ISAR generated images.

One public available instance is lava.xenomai.org. Example test runs
can be found at [1] with the CI triggers coming from the xenomai-images
project [2].

Florian

[1] https://lava.xenomai.org/scheduler/alljobs
[2] https://source.denx.de/Xenomai/xenomai-images

> 
> Felix
> 
> [1] https://github.com/siemens/mtda
> 
> > 
> > Uladzimir Bely (4):
> >   cibuilder.py: Refactor vm_start related functions
> >   testsuite: Add an interface to run commands over ssh
> >   testsuite: Separate common part of kas-based test example
> >   testsute: Provide an example of hardware test
> > 
> >  meta-isar/test/README.md                | 24 ++++++-
> >  meta-isar/test/common.sh                | 30 +++++++++
> >  meta-isar/test/run_test.sh              | 33 ++-------
> >  meta-isar/test/run_test_hw.sh           | 10 +++
> >  meta-isar/test/sample_kas_config_hw.yml | 32 +++++++++
> >  meta-isar/test/sample_test.py           |  0
> >  meta-isar/test/sample_test_hw.py        | 13 ++++
> >  testsuite/cibuilder.py                  | 89 +++++++++++++++++------
> > --
> >  8 files changed, 174 insertions(+), 57 deletions(-)
> >  create mode 100755 meta-isar/test/common.sh
> >  create mode 100755 meta-isar/test/run_test_hw.sh
> >  create mode 100644 meta-isar/test/sample_kas_config_hw.yml
> >  mode change 100644 => 100755 meta-isar/test/sample_test.py
> >  create mode 100755 meta-isar/test/sample_test_hw.py
> > 
> > -- 
> > 2.20.1
> > 
> 


  reply	other threads:[~2023-05-24  4:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  2:45 Uladzimir Bely
2023-05-24  2:45 ` [PATCH 1/4] cibuilder.py: Refactor vm_start related functions Uladzimir Bely
2023-05-24  2:45 ` [PATCH 2/4] testsuite: Add an interface to run commands over ssh Uladzimir Bely
2023-05-24  2:45 ` [PATCH 3/4] testsuite: Separate common part of kas-based test example Uladzimir Bely
2023-05-24  2:45 ` [PATCH 4/4] testsute: Provide an example of hardware test Uladzimir Bely
2023-05-24  3:06 ` [PATCH 0/4] Basic hardware testing support MOESSBAUER, Felix
2023-05-24  4:30   ` Florian Bezdeka [this message]
2023-05-24 11:37     ` Jan Kiszka
2023-05-31 21:01 ` Uladzimir Bely

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=01510fd6fb6722d661b7d23e6e3ba4f89440498f.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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