All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/bearssl: disable parallel build
Date: Mon, 17 Oct 2022 09:16:44 +0200	[thread overview]
Message-ID: <20221017091644.1104527b@windsurf> (raw)
In-Reply-To: <CADvTj4q+ztJca7+MEcOK5-gd94155C0X1s0_5-SvCxp=XXOptg@mail.gmail.com>

Hello James,

On Sun, 16 Oct 2022 12:45:06 -0400
James Hilliard <james.hilliard1@gmail.com> wrote:

> > Again, that is very interesting, but please, please, conordinate with
> > the rest of us when you do such changes, because that is very weird, as
> > Fabrice noted, to suddenly get build failures out of the blue when
> > nothing seemed to have otherwise changed.  
> 
> I've been experimenting a bit in general with autobuilder settings to try
> and fix some issues with poor coverage.
> 
> One other reason for testing with shuffle=random is to make higher kconfig
> probability values more useful(as otherwise build failures will be concentrated
> in packages early in the dependency ordering) :
> https://patchwork.ozlabs.org/project/buildroot/patch/20220514214612.3221647-1-james.hilliard1@gmail.com/

Thanks a lot for all this work, which I find really useful. However,
like Yann said I believe we need to coordinate better. I think we would
prefer to see build results submitted on autobuild.buildroot.org to
only be generated by the official/upstream autobuild-run script.
Otherwise, it's super confusing as we get results that corresponding to
variations of build configurations/build logic that we are not even
aware they exist.

Another concern is that the autobuilder results are already extremely
bad these days, and therefore the priority is more on addressing/fixing
the existing issues rather than adding more. It's a lot
easier/practical to fix new problems when they are not mixed together
with zillions of old problems.

Again, thanks a lot for your work on this!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-10-17  7:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15  0:58 [Buildroot] [PATCH 1/1] package/bearssl: disable parallel build James Hilliard
2022-10-15 22:14 ` Fabrice Fontaine
2022-10-15 23:21   ` James Hilliard
2022-10-16  7:50     ` Yann E. MORIN
2022-10-16 15:44       ` James Hilliard
2022-10-16 16:05         ` Yann E. MORIN
2022-10-16 16:45           ` James Hilliard
2022-10-17  7:16             ` Thomas Petazzoni via buildroot [this message]
2022-10-17 11:29               ` James Hilliard
2022-10-17 12:21                 ` Thomas Petazzoni via buildroot
2022-10-17 19:02                   ` James Hilliard
2022-10-30 20:29 ` Thomas Petazzoni via buildroot
2022-10-31  2:54   ` James Hilliard

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=20221017091644.1104527b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.