public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>,
	Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: docs@lists.yoctoproject.org, Quentin Schulz <foss@0leil.net>
Subject: Re: [docs] [PATCH v3] test-manual: add initial reproducible builds documentation
Date: Wed, 09 Jun 2021 17:30:56 +0100	[thread overview]
Message-ID: <6400f2c43fd9d292616cbc5d2f6cd99f98ebc2a3.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210609155552.nwjdirom4lkqi4n7@qschulz>

On Wed, 2021-06-09 at 17:55 +0200, Quentin Schulz wrote:
> On Wed, Jun 09, 2021 at 04:47:28PM +0200, Michael Opdenacker wrote:
> 
> > +
> > +You could subclass the test and change ``targets`` to a different target.
> > +
> > +You may also change ``sstate_targets`` which would allow you to "pre-cache" some
> > +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``.
> > -- 
> 
> I'm not sure this section has its place in our documentation since it
> seems bound to the current implementation and explains modifications of
> the code.
> 
> I'd vote it out.

Doesn't most of the manual document the current implementation?

When this wasn't here, you wanted an example! I do agree we should give people 
some kind of a hint about how to write their own tests. We're likely going to end 
up adding more example, not less?

Cheers,

Richard


  reply	other threads:[~2021-06-09 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1686F0ED5A1183FF.18579@lists.yoctoproject.org>
2021-06-09 14:47 ` [PATCH v3] test-manual: add initial reproducible builds documentation Michael Opdenacker
2021-06-09 15:55   ` [docs] " Quentin Schulz
2021-06-09 16:30     ` Richard Purdie [this message]
2021-06-10  8:54       ` Quentin Schulz
2021-06-10  9:14         ` Richard Purdie
2021-06-10 16:42           ` Quentin Schulz
2021-06-14 16:22     ` Michael Opdenacker
2021-06-09 16:43   ` Michael Opdenacker

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=6400f2c43fd9d292616cbc5d2f6cd99f98ebc2a3.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    --cc=michael.opdenacker@bootlin.com \
    --cc=quentin.schulz@streamunlimited.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