From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] autobuild-run: make diffoscope output to a JSON-formatted file
Date: Tue, 6 Aug 2019 21:40:14 +0200 [thread overview]
Message-ID: <20190806214014.52c8839b@windsurf.home> (raw)
In-Reply-To: <20190806181251.21885-4-itsatharva@gmail.com>
Hello Atharva,
On Tue, 6 Aug 2019 23:42:49 +0530
Atharva Lele <itsatharva@gmail.com> wrote:
> Normal diffoscope output is readable by humans but not really
> convenient when working with it in code. JSON can be easily
> read and extracted information from.
>
> Signed-off-by: Atharva Lele <itsatharva@gmail.com>
Peter and I had a look at the diffoscope output, and while the JSON
version is definitely good for human parsing, having the text version
in addition for humans to read would also be nice.
Could you instead store both the JSON and text versions ?
Just run this:
$ diffoscope --text differences.txt --json differences.json rootfs.tar rootfs.tar.before
And you'll get both the JSON and text version in files.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-06 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 18:12 [Buildroot] [PATCH 1/6] autobuild-run: use different output directories for reproducible builds testing Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 2/6] autobuild-run: make prepare_build() clean the output directory used for reproducibility testing Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 3/6] autobuild-run: fix cross tools prefix for diffoscope Atharva Lele
2019-08-06 20:18 ` Thomas Petazzoni
2019-08-06 18:12 ` [Buildroot] [PATCH 4/6] autobuild-run: make diffoscope output to a JSON-formatted file Atharva Lele
2019-08-06 19:40 ` Thomas Petazzoni [this message]
2019-08-07 6:12 ` Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 5/6] autobuild-run: initial implementation of get_reproducibility_failure_reason() Atharva Lele
2019-08-06 20:21 ` Thomas Petazzoni
2019-08-07 6:07 ` Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 6/6] autobuild-run: account for reproducibility failures in get_failure_reason() Atharva Lele
2019-08-06 19:37 ` [Buildroot] [PATCH 1/6] autobuild-run: use different output directories for reproducible builds testing Thomas Petazzoni
2019-08-07 6:02 ` Atharva Lele
2019-08-07 8:33 ` Thomas Petazzoni
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=20190806214014.52c8839b@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox