From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] utils/br-reproduce-build: handle reproducibility failures
Date: Thu, 26 Dec 2019 22:01:39 +0100 [thread overview]
Message-ID: <20191226220139.3d49d5ac@windsurf> (raw)
In-Reply-To: <20190825173635.23860-1-itsatharva@gmail.com>
Hello,
On Sun, 25 Aug 2019 23:06:35 +0530
Atharva Lele <itsatharva@gmail.com> wrote:
> Add a condition to check if the config has BR2_REPRODUCIBLE enabled and if it
> does, run the build in two output directories - output-1, output-2 - and then
> run diffoscope on the generated images.
>
> NOTE: You should have diffoscope installed in order to test reproducibility
> failures.
>
> Signed-off-by: Atharva Lele <itsatharva@gmail.com>
Thanks, I've applied to buildroot-test after doing some changes. See
below.
> +# Handle cases of testing reproducibility failures.
> +# Run the build in different output directories if BR2_REPRODUCIBLE=y
> +# and run diffoscope on the generated images. Output of diffoscope is
> +# saved in the "output-1" directory.
> +# NOTE: You should have diffoscope installed in order to test
> +# reproducibility failures.
> +if grep -Fxq "BR2_REPRODUCIBLE=y" "${BUILD_DIR}/config"; then
> + mkdir ../output-1 ../output-2
> + cp "${BUILD_DIR}/config" ../output-1/.config
> + cp "${BUILD_DIR}/config" ../output-2/.config
In the non-reproducible case, here we do an "olddefconfig" of the
configuration, so I've done the same, in both the output-1 and output-2
directories.
> + make 2>&1 O=../output-1 | tee logfile && make 2>&1 O=../output-2 | tee logfile
Here if the build fails we don't abort, we continue with the diffoscope
call, which will fail since the rootfs.tar doesn't exist, so I've added
a check for that.
Also, the "logfile" was overwriting itself: it is created in the
buildroot/ source directory, so it is common to both builds. So I
changed their name to logfile-1 and logfile-2.
> + PREFIX=$(make --no-print-directory O=../output-1 printvars VARS=TARGET_CROSS | cut -c 14- | head -c -1)
> + IMAGE_1="../output-1/images/rootfs.tar"
> + IMAGE_2="../output-2/images/rootfs.tar"
> + diffoscope ${IMAGE_1} ${IMAGE_2} --tool-prefix-binutils ${PREFIX} --text ../output-1/diffoscope_results.txt
> +else
> + mkdir ../output
> + cp "${BUILD_DIR}/config" ../output/.config
> + make olddefconfig O=../output/
> + make 2>&1 O=../output | tee logfile
> +fi
> \ No newline at end of file
And I added a newline character at the end of the file.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-12-26 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 17:36 [Buildroot] [PATCH] utils/br-reproduce-build: handle reproducibility failures Atharva Lele
2019-12-26 21:01 ` Thomas Petazzoni [this message]
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=20191226220139.3d49d5ac@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.