public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] Sstate-cache follow-up
Date: Tue, 22 Feb 2022 09:24:05 +0300	[thread overview]
Message-ID: <183f80ce-00fb-bac9-a743-ff33ff99533c@ilbers.de> (raw)
In-Reply-To: <20211223113400.1123555-1-adriaan.schmidt@siemens.com>

Can you please rebase on the current next so we can proceed with this 
patchset?
There are two main changes done so far:
1) CI test targets were updated
2) sstate tasks were changed

23.12.21 14:33, Adriaan Schmidt wrote:
> 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.
>
> 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     | 148 +++++++++++++++++++----------
>   testsuite/build_test/cibuilder.py  | 109 +++++++++++++++------
>   5 files changed, 248 insertions(+), 110 deletions(-)
>

      parent reply	other threads:[~2022-02-22  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 11:33 Adriaan Schmidt
2021-12-23 11:33 ` [PATCH 1/3] testsuite: refactor Adriaan Schmidt
2021-12-23 11:33 ` [PATCH 2/3] sstate: add test case Adriaan Schmidt
2021-12-23 11:34 ` [PATCH 3/3] doc: add sstate to user manual Adriaan Schmidt
2022-01-04 15:47 ` [PATCH 0/3] Sstate-cache follow-up Jan Kiszka
2022-01-07  8:18   ` Schmidt, Adriaan
2022-02-22  6:24 ` Anton Mikanovich [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=183f80ce-00fb-bac9-a743-ff33ff99533c@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=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