From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2018.11.1 released
Date: Thu, 20 Dec 2018 09:16:56 +0100 [thread overview]
Message-ID: <20181220091656.40397ad9@windsurf> (raw)
In-Reply-To: <87k1k5upbc.fsf@dell.be.48ers.dk>
Hello,
+Fabio for Freescale/NXP related build failures, +Ricardo for the
systemd test failure.
On Wed, 19 Dec 2018 23:25:27 +0100, Peter Korsgaard wrote:
> Buildroot 2018.11.1 is released - Go download it at:
Thanks for this release. There was a Gitlab CI run on the 2018.11.1
tag, see
https://gitlab.com/buildroot.org/buildroot/pipelines/40779740/builds.
We have only 3 failures on a total of 262 tests, which is not bad.
Here is a quick analysis:
imx6slevk_defconfig,
https://gitlab.com/buildroot.org/buildroot/-/jobs/136980040
freescale_imx7dsabresd_defconfig,
https://gitlab.com/buildroot.org/buildroot/-/jobs/136980027
Both of these look very similar to what was fixed by commit
1ad9c45a059deaaae65a78a9ed7f78b579fed422 in master, but this commit is
also in 2018.11.x.
However, commit 1ad9c45a059deaaae65a78a9ed7f78b579fed422 does not apply
to the failing defconfigs, as they don't use the patch added in
board/freescale/ by this commit.
Fabio, could you perhaps have a look ?
The last failure is on a systemd test, where it says that the boot
didn't work:
https://gitlab.com/buildroot.org/buildroot/-/jobs/136980206
However, looking at the boot log at
https://gitlab.com/buildroot.org/buildroot/-/jobs/136980206/artifacts/file/test-output/TestInitSystemSystemdRwFull-run.log,
it did boot, the login prompt appears.
Perhaps something for Ricardo ? :-)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-20 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 22:25 [Buildroot] Buildroot 2018.11.1 released Peter Korsgaard
2018-12-20 8:16 ` Thomas Petazzoni [this message]
2018-12-20 11:32 ` Fabio Estevam
2019-01-28 2:20 ` Ricardo Martincoski
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=20181220091656.40397ad9@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