public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v4 00/14] Update Avocado testsuite
Date: Wed, 21 Apr 2021 19:04:51 +0300	[thread overview]
Message-ID: <20210421160505.67194-1-amikan@ilbers.de> (raw)

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.
Original ci_build and vm_smoke_test are renamed to *_legacy.
Build and run logs are hidden now until an error occurs.

---
Changes since v3:
- Add automatic bitbake init.
- Fix line lengths.
- Fix build without repro.
- Fix build artifact paths.
- Prepare for Gitlab build.
- Change debug settings.
- Move log splitting to start_vm.
- Add deb package install.
Changes since v2:
- Make CI call Avocado tests.
- Wait less on vm_start test.
- Split Roman's vm_start commit.
- Put logs to build folder.
- Rearrange patches.
- Split build test to classes.
- Add test case tagging.
- Get rid of avocado-framework-plugin-varianter-yaml-to-mux.
- Get rid of python-subprocess32.
- Improve logging.
Changes since v1:
- Merge start_vm rebuild patches.
- Fix patch comments.

Anton Mikanovich (11):
  vm_boot_test: Fix log file path in vm_boot_test
  vm_boot_test: Remove external varianter
  vm_boot_test: Improve QEMU images checking
  build_test: Refactoring build tests cases
  testsuite: Add Python generations for testsuite in gitignore
  testsuite: Fix test suite prepare guide
  gitlab-ci: Add Avocado build artifacts
  vm_boot_test: Add automatic bitbake init
  ci_build: Migrate to Avocado
  vm_smoke_test: Migrate to Avocado
  ci_build: Install Avocado if needed

Roman Pletnev (3):
  start_vm.py: Fix target name handling
  start_vm.py: Add output and PID file vm_start.py options
  start_vm.py: Add MIPS support

 .gitlab-ci.yml                         |   1 +
 scripts/ci_build.sh                    | 215 ++++---------------
 scripts/ci_build_legacy.sh             | 275 +++++++++++++++++++++++++
 scripts/vm_smoke_test                  | 110 ++--------
 scripts/vm_smoke_test_legacy           | 168 +++++++++++++++
 testsuite/.gitignore                   |   1 +
 testsuite/README.md                    |  21 +-
 testsuite/build_test/build_test.py     | 137 ++++++++++--
 testsuite/build_test/cibase.py         | 122 +++++++++++
 testsuite/build_test/cibuilder.py      |  80 +++++++
 testsuite/build_test/run.sh            |   3 -
 testsuite/build_test/run_fast.sh       |   3 +
 testsuite/build_test/run_full.sh       |   3 +
 testsuite/build_test/variant.yaml      |  22 --
 testsuite/start_vm.py                  |  22 +-
 testsuite/vm_boot_test/run.sh          |   3 -
 testsuite/vm_boot_test/run_fast.sh     |   3 +
 testsuite/vm_boot_test/run_full.sh     |   3 +
 testsuite/vm_boot_test/variant.yaml    |  22 --
 testsuite/vm_boot_test/vm_boot_test.py | 120 +++++++++--
 20 files changed, 955 insertions(+), 379 deletions(-)
 create mode 100755 scripts/ci_build_legacy.sh
 create mode 100755 scripts/vm_smoke_test_legacy
 create mode 100644 testsuite/.gitignore
 create mode 100644 testsuite/build_test/cibase.py
 create mode 100644 testsuite/build_test/cibuilder.py
 delete mode 100755 testsuite/build_test/run.sh
 create mode 100755 testsuite/build_test/run_fast.sh
 create mode 100755 testsuite/build_test/run_full.sh
 delete mode 100644 testsuite/build_test/variant.yaml
 delete mode 100755 testsuite/vm_boot_test/run.sh
 create mode 100755 testsuite/vm_boot_test/run_fast.sh
 create mode 100755 testsuite/vm_boot_test/run_full.sh
 delete mode 100644 testsuite/vm_boot_test/variant.yaml

-- 
2.25.1


             reply	other threads:[~2021-04-21 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 16:04 Anton Mikanovich [this message]
2021-04-21 16:04 ` [PATCH v4 01/14] start_vm.py: Fix target name handling Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 02/14] start_vm.py: Add output and PID file vm_start.py options Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 03/14] start_vm.py: Add MIPS support Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 04/14] vm_boot_test: Fix log file path in vm_boot_test Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 05/14] vm_boot_test: Remove external varianter Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 06/14] vm_boot_test: Improve QEMU images checking Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 07/14] build_test: Refactoring build tests cases Anton Mikanovich
2021-04-21 16:04 ` [PATCH v4 08/14] testsuite: Add Python generations for testsuite in gitignore Anton Mikanovich
2021-04-21 16:05 ` [PATCH v4 09/14] testsuite: Fix test suite prepare guide Anton Mikanovich
2021-04-21 16:05 ` [PATCH v4 10/14] gitlab-ci: Add Avocado build artifacts Anton Mikanovich
2021-04-21 16:05 ` [PATCH v4 11/14] vm_boot_test: Add automatic bitbake init Anton Mikanovich
2021-04-21 16:05 ` [PATCH v4 12/14] ci_build: Migrate to Avocado Anton Mikanovich
2021-04-21 16:05 ` [PATCH v4 13/14] vm_smoke_test: " Anton Mikanovich
2021-04-21 16:05 ` [PATCH v4 14/14] ci_build: Install Avocado if needed 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=20210421160505.67194-1-amikan@ilbers.de \
    --to=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