From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
swat <swat@lists.yoctoproject.org>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
Steve Sakoman <steve@sakoman.com>,
Joshua Watt <jpewhacker@gmail.com>
Subject: Re: Autobuilder reproducibility target changes
Date: Sun, 14 Feb 2021 15:17:29 +0000 [thread overview]
Message-ID: <679f3ccb6bea88cd72132ba9ea51547e81bcf0d8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-cpgjuvUikfCrYCnBqTLdsNsY-5PUBji7PqJhkrbuHzg@mail.gmail.com>
On Sun, 2021-02-14 at 16:04 +0100, Alexander Kanavin wrote:
> Cheers :) If there's something else I could help, tell.
I'm going to try and get diffs of the remaining big package differences
and see where we stand. The two big ones I know of are go as a language
for reproducibility and perf. Perf will just be a shear pain to fix,
hopefully the kernel will take patches.
> One item is getting to the bottom of why it takes diffoscope beyond
> the heat death of the universe to render its verdict on some items.
That would be really helpful to get to the bottom of. The vim-common
difference is actually really simple:
https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20210213-0djxo1sn/packages/diff-html/
so I don't know why it took 5 hours to compute that. It suggests
something really silly/stupid is going on. diffoscope should be
amenable to fixes so it would be worth talking to them too...
(I have a fix for the locale problem in vim brewing, it needs a new
buildtools-extended-tarball)
Cheers,
Richard
next prev parent reply other threads:[~2021-02-14 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 12:19 Autobuilder reproducibility target changes Richard Purdie
2021-02-14 15:04 ` Alexander Kanavin
2021-02-14 15:17 ` Richard Purdie [this message]
2021-02-14 16:30 ` Alexander Kanavin
2021-02-14 18:47 ` Joshua Watt
2021-02-14 19:17 ` Joshua Watt
2021-02-15 6:21 ` Alexander Kanavin
2021-02-15 16:23 ` Joshua Watt
2021-02-15 16:31 ` Richard Purdie
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=679f3ccb6bea88cd72132ba9ea51547e81bcf0d8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=anuj.mittal@intel.com \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
--cc=swat@lists.yoctoproject.org \
/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