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 0/4] Improve variables obtaining in CI
Date: Wed, 31 Jan 2024 17:41:25 +0300	[thread overview]
Message-ID: <1d228589c724defff30d1609c16b53bcf68e5d0a.camel@ilbers.de> (raw)
In-Reply-To: <20240125090617.2945621-1-amikan@ilbers.de>

On Thu, 2024-01-25 at 11:06 +0200, Anton Mikanovich wrote:
> Reuse getVars API for as much cases as possible inside our CI to
> reduce
> external process creation overhead and speedup variables obtaining.
> This will also make this process much easier for testcase authors.
> 
> Anton Mikanovich (4):
>   CI: Fix getVars API self checks
>   CI: Remove getlayerdir API
>   CI: Reuse getVars in repro-build-test
>   CI: Use getVars for vm output checking
> 
>  testsuite/cibuilder.py        | 31 ++++++++++++++-----------------
>  testsuite/citest.py           |  2 +-
>  testsuite/repro-build-test.py |  8 +-------
>  3 files changed, 16 insertions(+), 25 deletions(-)
> 
> -- 
> 2.34.1
> 
Applied to next.

      parent reply	other threads:[~2024-01-31 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  9:06 Anton Mikanovich
2024-01-25  9:06 ` [PATCH 1/4] CI: Fix getVars API self checks Anton Mikanovich
2024-01-25  9:06 ` [PATCH 2/4] CI: Remove getlayerdir API Anton Mikanovich
2024-01-25  9:06 ` [PATCH 3/4] CI: Reuse getVars in repro-build-test Anton Mikanovich
2024-01-25  9:06 ` [PATCH 4/4] CI: Use getVars for vm output checking Anton Mikanovich
2024-01-31 14:41 ` 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=1d228589c724defff30d1609c16b53bcf68e5d0a.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