public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/7] Unify build and run test cases
Date: Wed, 23 Mar 2022 10:00:01 +0300	[thread overview]
Message-ID: <9c220792-d40f-249e-5c1b-fd1e09611e02@ilbers.de> (raw)
In-Reply-To: <20220316071647.8919-1-amikan@ilbers.de>

16.03.2022 10:16, Anton Mikanovich wrote:
> Make both build and start_vm CI tests run from one entry point to be
> able to manage CI in more flexible way.
> Also move QEMU boot logs into subdir to not flood ./build.
>
> Changes since v2:
> - Move timeout setting to unified test.
> Changes since v1:
> - Fix key paths for repro test.
>
> Anton Mikanovich (7):
>    CI: Reorganize testsuite folders
>    CI: Migrate all tests to one location
>    CI: Adopt vm_start test logging
>    CI: Do not run QEMU start tests from Gitlab
>    CI: Rename build_test.py to citest.py
>    CI: Change QEMU boot logs format
>    CI: Add timeout setting to ci_build
>
>   .gitlab-ci.yml                                |   4 +-
>   scripts/ci_build.sh                           |  21 ++-
>   scripts/vm_smoke_test                         |   4 +-
>   testsuite/README.md                           |  26 +++-
>   testsuite/build_test/run_fast.sh              |   3 -
>   testsuite/build_test/run_full.sh              |   3 -
>   testsuite/{build_test => }/cibase.py          |   4 +-
>   testsuite/{build_test => }/cibuilder.py       |  80 ++++++++++-
>   .../{build_test/build_test.py => citest.py}   |  46 ++++++
>   testsuite/{ => keys}/base-apt/test_priv.key   |   0
>   testsuite/{ => keys}/base-apt/test_pub.key    |   0
>   testsuite/vm_boot_test/run_fast.sh            |   3 -
>   testsuite/vm_boot_test/run_full.sh            |   3 -
>   testsuite/vm_boot_test/vm_boot_test.py        | 133 ------------------
>   14 files changed, 172 insertions(+), 158 deletions(-)
>   delete mode 100755 testsuite/build_test/run_fast.sh
>   delete mode 100755 testsuite/build_test/run_full.sh
>   rename testsuite/{build_test => }/cibase.py (97%)
>   mode change 100644 => 100755
>   rename testsuite/{build_test => }/cibuilder.py (69%)
>   mode change 100644 => 100755
>   rename testsuite/{build_test/build_test.py => citest.py} (87%)
>   mode change 100644 => 100755
>   rename testsuite/{ => keys}/base-apt/test_priv.key (100%)
>   rename testsuite/{ => keys}/base-apt/test_pub.key (100%)
>   delete mode 100755 testsuite/vm_boot_test/run_fast.sh
>   delete mode 100755 testsuite/vm_boot_test/run_full.sh
>   delete mode 100644 testsuite/vm_boot_test/vm_boot_test.py

Applied to next.


      parent reply	other threads:[~2022-03-23  7:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16  7:16 Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 1/7] CI: Reorganize testsuite folders Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 2/7] CI: Migrate all tests to one location Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 3/7] CI: Adopt vm_start test logging Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 4/7] CI: Do not run QEMU start tests from Gitlab Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 5/7] CI: Rename build_test.py to citest.py Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 6/7] CI: Change QEMU boot logs format Anton Mikanovich
2022-03-16  7:16 ` [PATCH v3 7/7] CI: Add timeout setting to ci_build Anton Mikanovich
2022-03-23  7:00 ` Anton Mikanovich [this message]

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=9c220792-d40f-249e-5c1b-fd1e09611e02@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