From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
OE-core <openembedded-core@lists.openembedded.org>,
Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Subject: Re: [OE-core] [PATCH 1/4] recipetool: Set master branch only as fallback
Date: Wed, 8 Dec 2021 09:10:17 +0100 [thread overview]
Message-ID: <CANNYZj9W613_D++e=OH63rE1=rRAciziOKM439Yw4nxLai7ymA@mail.gmail.com> (raw)
In-Reply-To: <3cda9bd5-1c75-7269-921c-97c1ac6c4fb5@weidmueller.com>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Wed, 8 Dec 2021 at 08:45, Stefan Herbrechtsmeier <
stefan.herbrechtsmeier-oss@weidmueller.com> wrote:
> I will update my patch series but need some time to test it locally. The
> devtool test build a lot of recipe on every run because it use a private
> sstate cache. How does the autobuilder overcome this problem?
>
If you don't rebase the branch used for testing, and set the cache to a
directory outside of build directory (e.g. /home/stefan/sstate ) it will
reuse that cache between selftest invocations.
The autobuilder uses a single writeable cache for all builds and builders,
mounted as read-write NFS partition.
Alex
[-- Attachment #2: Type: text/html, Size: 1066 bytes --]
next prev parent reply other threads:[~2021-12-08 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 8:04 [PATCH 1/4] recipetool: Set master branch only as fallback Stefan Herbrechtsmeier
2021-12-06 8:04 ` [PATCH 2/4] selftest/recipetool: Split tests into separate test classes Stefan Herbrechtsmeier
2021-12-06 8:04 ` [PATCH 3/4] selftest/recipetool: Add tests for branch parameter and srcbranch option Stefan Herbrechtsmeier
2021-12-06 8:04 ` [PATCH 4/4] selftest: devtool: Separate common functions and devtool sstate setup into two classes Stefan Herbrechtsmeier
2021-12-07 15:45 ` [OE-core] [PATCH 1/4] recipetool: Set master branch only as fallback Richard Purdie
2021-12-08 7:45 ` Stefan Herbrechtsmeier
2021-12-08 8:10 ` Alexander Kanavin [this message]
2021-12-08 8:27 ` Stefan Herbrechtsmeier
2021-12-08 8:32 ` Alexander Kanavin
2021-12-08 8:48 ` Stefan Herbrechtsmeier
2021-12-08 9:13 ` Richard Purdie
2021-12-08 9:12 ` Richard Purdie
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='CANNYZj9W613_D++e=OH63rE1=rRAciziOKM439Yw4nxLai7ymA@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=stefan.herbrechtsmeier-oss@weidmueller.com \
--cc=stefan.herbrechtsmeier@weidmueller.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.