From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] autobuild-run: initial implementation of do_reproducible_build()
Date: Fri, 7 Jun 2019 10:44:34 +0200 [thread overview]
Message-ID: <20190607104434.7ba3712d@windsurf> (raw)
In-Reply-To: <e4f040d2-1b8c-73a1-9142-eb4dac4a3570@mind.be>
On Fri, 7 Jun 2019 10:39:40 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> Exactly.
>
> Though the solution with a different output path is probably even simpler, in
> the end.
>
> The issue, though, is that it requires a bit of refactoring of the
> autobuild-run code, so it takes a bit of time to develop and even more time to
> review. On the other hand, we want to start running reproducibility tests as
> soon as possible, so we can get some results from the autobuilders and have an
> idea of how bad it is.
Makes sense.
> Therefore, we've chosen to resubmit the patches with the same output dir and
> hope that they can be applied quickly. Hint, hint :-)
Hehe :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-07 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 6:46 [Buildroot] [PATCH v2 1/3] autobuild-run: initial implementation of check_reproducibility() Atharva Lele
2019-06-07 6:46 ` [Buildroot] [PATCH v2 2/3] autobuild-run: initial implementation of do_reproducible_build() Atharva Lele
2019-06-07 8:33 ` Thomas Petazzoni
2019-06-07 8:39 ` Arnout Vandecappelle
2019-06-07 8:44 ` Thomas Petazzoni [this message]
2019-06-07 8:40 ` Atharva Lele
2019-06-08 11:40 ` Arnout Vandecappelle
2019-06-07 6:46 ` [Buildroot] [PATCH v2 3/3] autobuild-run: do reproducible builds tests if BR2_REPRODUCIBLE=y Atharva Lele
2019-06-08 11:46 ` Arnout Vandecappelle
2019-06-08 11:37 ` [Buildroot] [PATCH v2 1/3] autobuild-run: initial implementation of check_reproducibility() Arnout Vandecappelle
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=20190607104434.7ba3712d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.