public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH v2 0/3] Sstate-cache follow-up
Date: Tue, 22 Feb 2022 10:06:25 +0100	[thread overview]
Message-ID: <20220222090628.2174022-1-adriaan.schmidt@siemens.com> (raw)

This adds the test case for the sstate-cache that we postponed
when merging the original sstate series.
It also includes the current draft from our discussion of changes
to the testsuite itself (rebased on next).

And some basic documentation of the sstate feature. It does not go into
any details on how to operate a deployment with (shared) caches in
practice. We're still gathering experience with that ourselves, but at some
point I hope we can provide some best-practice recommendations and
a script/utility for cache maintenance.

changes since v1:
- rebase on next
- add check to verify contents of deploy dir when using sstate caching

Adriaan Schmidt (3):
  testsuite: refactor
  sstate: add test case
  doc: add sstate to user manual

 doc/user_manual.md                 |  24 ++++
 scripts/ci_build.sh                |  22 ++--
 testsuite/build_test/build_test.py |  55 +++++++---
 testsuite/build_test/cibase.py     | 171 +++++++++++++++++++----------
 testsuite/build_test/cibuilder.py  | 109 +++++++++++++-----
 5 files changed, 262 insertions(+), 119 deletions(-)

-- 
2.30.2


             reply	other threads:[~2022-02-22  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  9:06 Adriaan Schmidt [this message]
2022-02-22  9:06 ` [PATCH v2 1/3] testsuite: refactor Adriaan Schmidt
2022-02-22  9:06 ` [PATCH v2 2/3] sstate: add test case Adriaan Schmidt
2022-02-22  9:06 ` [PATCH v2 3/3] doc: add sstate to user manual Adriaan Schmidt
2022-02-28 15:30 ` [PATCH v2 0/3] Sstate-cache follow-up Anton Mikanovich

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=20220222090628.2174022-1-adriaan.schmidt@siemens.com \
    --to=adriaan.schmidt@siemens.com \
    --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