From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Short question about: [autobuild.buildroot.net] Your build results for 2019-04-14
Date: Mon, 15 Apr 2019 14:39:10 +0200 [thread overview]
Message-ID: <20190415143910.7580f187@windsurf> (raw)
In-Reply-To: <alpine.DEB.2.20.1904150914260.19094@defender.svolli.xa>
Hello Sven,
On Mon, 15 Apr 2019 09:18:08 +0200 (CEST)
Sven Oliver Moll <svolli@svolli.de> wrote:
> Hello Thomas,
>
> I've got a question about this build fail. I'm pretty sure, Arnout fixed
> this already:
> https://git.busybox.net/buildroot/commit/?id=152a3f0be3ae180a470c7a7d86b363bd0af18d02
>
> Let's assume I'm wrong. Will I then get another mail, if the build fails
> again?
The autobuilder result you're pointing to, i.e
http://autobuild.buildroot.net/results/c7540203a8eadad3f324f0d7e7fe66a526d4a2e9,
has a file that indicates which Buildroot Git commit was used when the
build was done:
http://autobuild.buildroot.net/results/c7540203a8eadad3f324f0d7e7fe66a526d4a2e9/gitid
It says 51d6d6c580432435f2b2f95ed35e22a5ecbe9dcb, which indeed predates
commit 152a3f0be3ae180a470c7a7d86b363bd0af18d02, where parallel build
for 'most' was disabled.
So indeed, it is very likely that Arnout's patch fixed this issue.
You'll receive other e-mail reports if there are other build failures.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
parent reply other threads:[~2019-04-15 12:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.DEB.2.20.1904150914260.19094@defender.svolli.xa>]
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=20190415143910.7580f187@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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