From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fabien Thomas <fabien.thomas@smile.fr>, yocto@lists.yoctoproject.org
Cc: Yoann Congal <yoann.congal@smile.fr>
Subject: Re: [yocto] [yocto-autobuilder-helper][PATCH v2] config.json: add reproducible-openembedded build
Date: Thu, 05 Oct 2023 22:51:45 +0100 [thread overview]
Message-ID: <a1f9a4b2816d9f048d9ef04d20a6a21b5663ecd7.camel@linuxfoundation.org> (raw)
In-Reply-To: <178B4DC19A31CF35.3256@lists.yoctoproject.org>
On Thu, 2023-10-05 at 20:46 +0100, Richard Purdie via
lists.yoctoproject.org wrote:
> On Thu, 2023-10-05 at 17:42 +0100, Richard Purdie via
> lists.yoctoproject.org wrote:
> > On Mon, 2023-10-02 at 16:54 +0200, Fabien Thomas wrote:
> > > The purpose of this new builder is to report the reproducibility status
> > > of all meta-openembedded recipes layer by layer. It use the same
> > > reproducible selftest than OE-Core but setting only world as target,
> > > and excluding all oecore and other openembedded layer recipes.
> > > Also, the report output directory is split by layers.
> > >
> > > Signed-off-by: Fabien Thomas <fabien.thomas@smile.fr>
> > > Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
> > > ---
> > >
> > > Changes v1->v2 :
> > > * Split builder into multiple steps, one for each openembedded layers.
> > > * Split reports output in the same way, one for each layers.
> > > * For each step, only to be tested layer and its dependancies are added.
> > > * Every other layers than the one that is tested is excluded from world.
> >
> > Thanks, I've merged this with a tweak of "reproducible-meta-
> > openembedded" -> "reproducible-meta-oe" just to keep things more
> > readable in the UI.
> >
> > There is a test run queued here:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/buildrequests/454516?redirect_to_build=true
> >
> > but things are a bit busy atm on the autobuilder so it is queued.
>
> That broke as did the second attempt. I've pushed controller side
> tweaks and some tweaks to helper which means this is now running:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/3
>
> Obviously there are still some failures but it is doing more this time
> and a least running something in some steps.
Whilst a lot of it failed, there was one piece that succeeded and
generated diffoscope output:
https://autobuilder.yoctoproject.org/typhoon/#/builders/155/builds/3/steps/21/logs/stdio
http://autobuilder.yocto.io/pub/repro-fail-openembedded-meta-initramfs/oe-reproducible-20231005-y6zo9rio/packages/diff-html/
As well as fixing the failures, the "short" names need work to make the
UI readable.
Cheers,
Richard
next prev parent reply other threads:[~2023-10-05 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:54 [yocto-autobuilder-helper][PATCH v2] config.json: add reproducible-openembedded build Fabien Thomas
2023-10-02 17:16 ` [yocto] " Khem Raj
2023-10-05 16:42 ` Richard Purdie
[not found] ` <178B43BD6DF66AF4.3256@lists.yoctoproject.org>
2023-10-05 19:46 ` Richard Purdie
[not found] ` <178B4DC19A31CF35.3256@lists.yoctoproject.org>
2023-10-05 21:51 ` Richard Purdie [this message]
2023-10-06 14:27 ` Fabien THOMAS
2023-10-11 8:38 ` Alexander Kanavin
2023-10-11 9:26 ` Jose Quaresma
2023-10-13 14:41 ` Fabien Thomas
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=a1f9a4b2816d9f048d9ef04d20a6a21b5663ecd7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fabien.thomas@smile.fr \
--cc=yoann.congal@smile.fr \
--cc=yocto@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