Buildroot Archive on 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 14:21:09 +0200	[thread overview]
Message-ID: <20221017142109.424863e1@windsurf> (raw)
In-Reply-To: <CADvTj4qT7BZY4QhkC0A=LFQ5x2fgWBAdECaAGFxu5VUE=ukgxw@mail.gmail.com>

On Mon, 17 Oct 2022 07:29:52 -0400
James Hilliard <james.hilliard1@gmail.com> wrote:

> The shuffle=random changes don't require modifying autobuild-run, I'm
> just tweaking the path to make in my autobuild service environment and
> then passing an additional config flag to autobuild-run like this:
> --make-opts="--shuffle=random"

Right, but my point stands: it's custom usage/configuration of
autobuild-run that we would prefer to discuss on the mailing list first
before deploying/enabling.

> Well builds were mostly failing in the same place due to deterministic
> build ordering, I was trying to make it so that we would see failures
> in different places as that's more useful compared with always seeing
> the same errors.
> 
> To me seeing the same errors most of the time indicates there's some
> major coverage issues with the autobuilders which need fixing.

I think you're missing a point here: many of the builds today are
failing due to the glibc 2.36 bump. So pretty much every single build
that is glibc based will indeed fail with some error related to this
glibc bump.

Your additional randomization will not change anything to this. It's
just that we now have the glibc bump issues + the newly discovered
issues related to the extra randomization + the usual amount of build
issues.

Best regards,

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 12:21 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
2022-10-17 11:29               ` James Hilliard
2022-10-17 12:21                 ` Thomas Petazzoni via buildroot [this message]
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=20221017142109.424863e1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox