public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/5] Remove code duplications for start_vm
Date: Wed, 26 Jun 2024 09:32:32 +0300	[thread overview]
Message-ID: <ed7440ce2c7a86b2b1ad33de630a38c07f886ac1.camel@ilbers.de> (raw)
In-Reply-To: <20240621150814.189288-1-amikan@ilbers.de>

On Fri, 2024-06-21 at 18:08 +0300, Anton Mikanovich wrote:
> We had both shell and python APIs for running QEMU images, there is
> also start_vm related functionality in testsuite itself. All this
> parts
> duplicate each other and should be cleanup.
> 
> Changes since v2:
> - Fix getVars usage in repro-build-test.
> - Fix coding style.
> 
> Changes since v1:
> - Fix multiple image type targets.
> 
> Anton Mikanovich (3):
>   start_vm: Add secureboot support
>   CI: Allow external usage for some APIs
>   start_vm: Reuse getVars API
> 
> Ilia Skochilov (2):
>   start_vm: Switch to python version
>   scripts: Remove vm_smoke_test
> 
>  CONTRIBUTING.md                          |  50 +++----
>  meta-isar/conf/machine/qemuamd64-sb.conf |   2 +-
>  scripts/start_vm                         | 161 ++-------------------
> --
>  scripts/vm_smoke_test                    | 106 ---------------
>  testsuite/README.md                      |   4 +-
>  testsuite/cibase.py                      |   8 +-
>  testsuite/cibuilder.py                   |  69 +++-------
>  testsuite/citest.py                      |   4 +-
>  testsuite/repro-build-test.py            |   4 +-
>  testsuite/start_vm.py                    |  94 +++++++++----
>  testsuite/utils.py                       |  55 ++++++++
>  11 files changed, 193 insertions(+), 364 deletions(-)
>  delete mode 100755 scripts/vm_smoke_test
>  create mode 100755 testsuite/utils.py
> 
> -- 
> 2.34.1
> 

Applied to next.

-- 
Best regards,
Uladzimir.

      parent reply	other threads:[~2024-06-26  6:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 15:08 Anton Mikanovich
2024-06-21 15:08 ` [PATCH v3 1/5] start_vm: Switch to python version Anton Mikanovich
2024-06-21 15:08 ` [PATCH v3 2/5] start_vm: Add secureboot support Anton Mikanovich
2024-06-21 15:08 ` [PATCH v3 3/5] scripts: Remove vm_smoke_test Anton Mikanovich
2024-06-21 15:08 ` [PATCH v3 4/5] CI: Allow external usage for some APIs Anton Mikanovich
2024-06-21 15:08 ` [PATCH v3 5/5] start_vm: Reuse getVars API Anton Mikanovich
2024-06-26  6:32 ` Uladzimir Bely [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=ed7440ce2c7a86b2b1ad33de630a38c07f886ac1.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=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