public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/3] Improve testsuite and fix bootstrap sstate issue
Date: Thu, 14 Sep 2023 12:43:10 +0200	[thread overview]
Message-ID: <20230914104313.30231-1-ubely@ilbers.de> (raw)

Patches 1-2 modify testsuite so that sstate cache populating is done
from a separate Isar location.

This allows to find issues that can't be detected when the same Isar
location used for populating and reusing sstate-cache.

Patch 3 (previously sent separately) fixes such an issue found in
isar-bootsrap routines.

Uladzimir Bely (3):
  testsuite: Allow using custom isar location in test initialization
  testsuite: Rework cache populating of sstate-cache in SstateTest
  isar-bootstrap: Avoid absolute paths in SRC_URI

 .../isar-bootstrap/isar-bootstrap.inc         |  8 +++---
 testsuite/cibase.py                           | 26 ++++++++++++++-----
 testsuite/cibuilder.py                        |  6 ++---
 testsuite/citest.py                           |  6 +++++
 4 files changed, 31 insertions(+), 15 deletions(-)

-- 
2.20.1


             reply	other threads:[~2023-09-14 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 10:43 Uladzimir Bely [this message]
2023-09-14 10:43 ` [PATCH 1/3] testsuite: Allow using custom isar location in test initialization Uladzimir Bely
2023-09-14 10:43 ` [PATCH 2/3] testsuite: Rework cache populating of sstate-cache in SstateTest Uladzimir Bely
2023-09-14 10:43 ` [PATCH 3/3] isar-bootstrap: Avoid absolute paths in SRC_URI Uladzimir Bely
2023-09-19  4:18 ` [PATCH 0/3] Improve testsuite and fix bootstrap sstate issue Uladzimir Bely

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=20230914104313.30231-1-ubely@ilbers.de \
    --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