public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 00/12] Next avocado improvements​
Date: Tue, 07 Mar 2023 07:10:33 +0300	[thread overview]
Message-ID: <2024182.YKUYFuaPT4@home> (raw)
In-Reply-To: <20230303144727.481716-1-amikan@ilbers.de>

In the email from Friday, 3 March 2023 17:47:15 +03 user Anton Mikanovich wrote:
> There are several ways of improving Isar testsuite currently:
> 1) Simplify testsuite configuring. Beside of making CI more comfortable for user
> it will also move us closer to removing ci_build.sh at all and just execute
> avocado with some minimal parameters.
> 2) Reusing of caches. This will be helpful later on after moving to parallel
> test cases execution.
> 3) Improve testsuite documentation
> 4) Moving avocado binary up to date
> All this improvements can be found in the following patchset.
> 
> Changes since v1:
> - Rebased on next
> - Fix typos in commit messages
> - Add Jenkinsfile
> 
> Anton Mikanovich (10):
>   CI: Update Avocado version
>   CI: Add avocado version checking
>   CI: Set default QEMU timeout to 10 minutes
>   CI: Make quiet option to be set by default
>   CI: Remove norun option
>   CI: Enable sstate dir sharing
>   CI: Enable ccache dir sharing
>   CI: Add Jenkins pipeline configuration
>   CI: Update avocado install documentation
>   CI: Add documentation for test case creation
> 
> Uladzimir Bely (2):
>   scripts: Add option to directly specify avocado tags
>   gitlab-ci.yml: Run dev tests set on push
> 
>  .gitlab-ci.yml         | 13 ++++++++---
>  Jenkinsfile            | 34 +++++++++++++++++++++++++++++
>  scripts/ci_build.sh    | 49 ++++++++++++++++++++++++++++--------------
>  testsuite/README.md    | 48 +++++++++++++++++++++++++++++++++++------
>  testsuite/cibase.py    |  8 +++----
>  testsuite/cibuilder.py | 18 +++++++++++++---
>  6 files changed, 137 insertions(+), 33 deletions(-)
>  create mode 100644 Jenkinsfile
> 
> 

Merged to next (patches 02 and 10 excluded).



      parent reply	other threads:[~2023-03-07  4:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 14:47 Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 01/12] CI: Update Avocado version Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 02/12] CI: Add avocado version checking Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 03/12] scripts: Add option to directly specify avocado tags Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 04/12] gitlab-ci.yml: Run dev tests set on push Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 05/12] CI: Set default QEMU timeout to 10 minutes Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 06/12] CI: Make quiet option to be set by default Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 07/12] CI: Remove norun option Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 08/12] CI: Enable sstate dir sharing Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 09/12] CI: Enable ccache " Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 10/12] CI: Add Jenkins pipeline configuration Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 11/12] CI: Update avocado install documentation Anton Mikanovich
2023-03-03 14:47 ` [PATCH v2 12/12] CI: Add documentation for test case creation Anton Mikanovich
2023-03-07  4:10 ` 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=2024182.YKUYFuaPT4@home \
    --to=ubely@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