All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] ref-manual: tasks: do_cleanall: mention it is not allowed with a shared DL_DIR
Date: Tue, 20 Feb 2024 08:58:27 +0100	[thread overview]
Message-ID: <20240220085828.00300bdf@booty> (raw)
In-Reply-To: <d7177c8d-756e-41ab-95aa-6e7b8ccb591b@theobroma-systems.com>

Hi Quentin,

On Mon, 19 Feb 2024 17:12:46 +0100
Quentin Schulz <quentin.schulz@theobroma-systems.com> wrote:

> Hi Luca,
> 
> On 2/19/24 16:55, Luca Ceresoli via lists.yoctoproject.org wrote:
> > [You don't often get email from luca.ceresoli=bootlin.com@lists.yoctoproject.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > 
> > do_cleanall can produce failures if using a shared download directory. This
> > is why it is forbidden when writing tests that will run on the autobuilders
> > (https://docs.yoctoproject.org/test-manual/intro.html?highlight=cleanall#considerations-when-writing-tests).
> > 
> > Reported-by: Sam Liddicott
> > Link: https://bootlin.com/blog/yocto-sharing-the-sstate-cache-and-download-directories/#comment-2650335
> > Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> > ---
> >   documentation/ref-manual/tasks.rst | 13 +++++++++++++
> >   1 file changed, 13 insertions(+)
> > 
> > diff --git a/documentation/ref-manual/tasks.rst b/documentation/ref-manual/tasks.rst
> > index 0db960b22f80..c754eb15514b 100644
> > --- a/documentation/ref-manual/tasks.rst
> > +++ b/documentation/ref-manual/tasks.rst
> > @@ -474,6 +474,19 @@ Typically, you would not normally use the :ref:`ref-tasks-cleanall` task. Do so
> >   if you want to start fresh with the :ref:`ref-tasks-fetch`
> >   task.
> > 
> > +.. note::
> > +
> > +   Never run the :ref:`ref-tasks-cleanall` task if your :term:`DL_DIR` is  
> 
> This also applies if SSTATE_DIR is shared I believe?

I don't think so. As far as I understand the sstate cache, a cache
entry is either found or not found, while for the downloads there is
the strange state of having a do_fetch stamp but no downloaded archive.

However I may be wrong. Do you have an example command sequence where
do_cleansstate can create a build failure?

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2024-02-20  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 15:55 [PATCH] ref-manual: tasks: do_cleanall: mention it is not allowed with a shared DL_DIR Luca Ceresoli
2024-02-19 16:12 ` [docs] " Quentin Schulz
2024-02-20  7:58   ` Luca Ceresoli [this message]
2024-02-20  9:01     ` Richard Purdie
2024-02-20 10:20       ` Quentin Schulz

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=20240220085828.00300bdf@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@theobroma-systems.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.