All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: yoann.congal@smile.fr, docs@lists.yoctoproject.org
Cc: Guillaume Swaenepoel <guillaume.swaenepoel@smile.fr>
Subject: Re: [docs] [PATCH 3/3] reproducible-builds: add a "How to" section with OEQA* variables
Date: Thu, 6 Feb 2025 17:08:48 +0100	[thread overview]
Message-ID: <6a34b601-8ddb-4101-9ae9-d0996202f79e@cherry.de> (raw)
In-Reply-To: <20250206131811.86935-3-yoann.congal@smile.fr>

Hi Yoann,

On 2/6/25 2:18 PM, Yoann Congal via lists.yoctoproject.org wrote:
> From: Yoann Congal <yoann.congal@smile.fr>
> 
> Shows an example of the new variable OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS
> and still mention OEQA_REPRODUCIBLE_TEST_TARGET/SSTATE_TARGETS that were
> shown earlier.
> 
> Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
> Reviewed-by: Guillaume Swaenepoel <guillaume.swaenepoel@smile.fr>
> ---
>   .../test-manual/reproducible-builds.rst        | 18 ++++++++++++++++++
>   1 file changed, 18 insertions(+)
> 
> diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst
> index b9f671d68..909ac5216 100644
> --- a/documentation/test-manual/reproducible-builds.rst
> +++ b/documentation/test-manual/reproducible-builds.rst
> @@ -145,3 +145,21 @@ set of recipes before the test, meaning they are excluded from reproducibility
>   testing. As a practical example, you could set ``sstate_targets`` to
>   ``core-image-sato``, then setting ``targets`` to ``core-image-sato-sdk`` would
>   run reproducibility tests only on the targets belonging only to ``core-image-sato-sdk``.
> +
> +Using OEQA_REPRODUCIBLE_TEST_* variables

I think it'd make sense here to tick-quote OEQA_REPRODUCIBLE_TEST_*?

> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +If you want to test the reproducibility of a set of recipe, you can define

s/recipe/recipes/

> +:term:`OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS`, in your local.conf::
> +
> +    OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS = "my-recipe"
> +

We align by three whitespaces, and I think it's four here if my eyes 
don't fail me?

> +This will test the reproducibility of ``my-recipe`` but will use the
> +:ref:`Shared State <overview-manual/concepts:Shared State>` for most its
> +dependencies.
> +
> +You can have finer control on the test with:
> +
> +- :term:`OEQA_REPRODUCIBLE_TEST_TARGET`: lists recipes to be built,

Reading this I'm wondering if this includes the recipes that will be 
built using sstate-cache as well, i.e. all recipes that will be built?

Cheers,
Quentin


  reply	other threads:[~2025-02-06 16:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 13:18 [PATCH 1/3] ref-manual/variables: document OEQA_REPRODUCIBLE_TEST_LEAF_TARGETS Yoann Congal
2025-02-06 13:18 ` [PATCH 2/3] reproducible-builds: change/add titles in the "How" section Yoann Congal
2025-02-06 13:18 ` [PATCH 3/3] reproducible-builds: add a "How to" section with OEQA* variables Yoann Congal
2025-02-06 16:08   ` Quentin Schulz [this message]
2025-02-06 18:17     ` [docs] " Yoann Congal
2025-02-07  9:12       ` Quentin Schulz
2025-02-09 22:46         ` Yoann Congal
2025-02-10 12:11           ` Antonin Godard
2025-02-10 17:52           ` Quentin Schulz
2025-02-11 23:37             ` Yoann Congal

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=6a34b601-8ddb-4101-9ae9-d0996202f79e@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=docs@lists.yoctoproject.org \
    --cc=guillaume.swaenepoel@smile.fr \
    --cc=yoann.congal@smile.fr \
    /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.