From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
James Hilliard <james.hilliard1@gmail.com>,
buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Giulio Benetti <giulio.benetti@micronovasrl.com>,
Adam Duskett <aduskett@gmail.com>
Subject: Re: [Buildroot] Some analysis of the major build failure reasons
Date: Tue, 3 Aug 2021 12:11:57 +0200 [thread overview]
Message-ID: <20210803121157.54af210b@windsurf> (raw)
In-Reply-To: <3430ac54-09ee-c25f-1dd3-82035c3d87a0@mind.be>
Hello,
On Tue, 3 Aug 2021 12:04:13 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> A simpler solution is to use 'make -Orecurse' or 'make -Otarget'. That keeps
> the recursive output together.
True, but as you say below, it doesn't guarantee that the actual issue
appears in the last part of the build log.
> It may not fully help due to the "Waiting for unfinished jobs" bit - the line
> with the failed package may appear just before that. But that can be solved by
> first searching the "Waiting for unfinished jobs" line and cutting off
> everything after it.
True. Needs some logic in extract_end_log() in autobuild-run.
So what should we do ? Build with -Otarget, and keep the last ~500
lines before the "Waiting for unfinished jobs" ?
> Additional autobuilders do help because they offer a different build
> environment. If there's some autobuild failure that *doesn't* happen on James's
> machines, you can be sure that it's due to the build environment.
Absolutely true, that's a very good point that you have here.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-03 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 6:09 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-08-01 Thomas Petazzoni
2021-08-02 21:46 ` [Buildroot] Some analysis of the major build failure reasons Thomas Petazzoni
2021-08-02 22:56 ` Giulio Benetti
2021-08-02 23:38 ` Giulio Benetti
2021-08-03 2:43 ` James Hilliard
2021-08-03 6:29 ` Giulio Benetti
2021-08-03 7:28 ` Thomas Petazzoni
2021-08-03 10:04 ` Arnout Vandecappelle
2021-08-03 10:11 ` Thomas Petazzoni [this message]
2021-08-03 14:41 ` Arnout Vandecappelle
2021-08-03 12:24 ` Giulio Benetti
2021-08-03 12:48 ` Giulio Benetti
2021-08-04 10:04 ` Giulio Benetti
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=20210803121157.54af210b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=aduskett@gmail.com \
--cc=arnout@mind.be \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=giulio.benetti@micronovasrl.com \
--cc=james.hilliard1@gmail.com \
/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.