From: Stephane Viau (OSS) <stephane.viau@oss.nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-01-15
Date: Mon, 18 Jan 2021 10:26:27 +0000 [thread overview]
Message-ID: <PA4PR04MB7920C4990EEA59953B4C3C4DA7A40@PA4PR04MB7920.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <6fdd08ad-8de6-464b-a7b2-47c9cbedad77@HE1EUR01FT006.eop-EUR01.prod.protection.outlook.com>
>________________________________________
>From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
>Sent: Saturday, January 16, 2021 8:18 AM
>To: Stephane Viau (OSS)
>Subject: [autobuild.buildroot.net] Your daily results for 2021-01-15
>
>Hello,
>
>Gitlab CI failures
>==================
>
>Below is a list of Gitlab CI job failures in relation to defconfigs
>or runtime tests you are in charge of. Please help us
>improving the quality of Buildroot by investigating
>those build failures and sending patches to fix
>them.Thanks!
>
>Results for 'master'
>--------------------
>
>Build failures related to your defconfigs:
>
> defconfig | link to the job
>----------------------------------+--------------------------------------------------------------
> freescale_imx8mnevk | https://gitlab.com/buildroot.org/buildroot/-/jobs/962451205
>
Hello Thomas, Yann,
Today, none of the freescale_imx* defconfig build on master.
A git bisect blames commit 5b95a5dc2 ("support/download: change format of
archives generated from git"), introduced by Yann on January 10th.
Any idea whether someone is looking into these failures?
BR,
Stephane.
>
>
>--
>http://autobuild.buildroot.net
next parent reply other threads:[~2021-01-18 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fdd08ad-8de6-464b-a7b2-47c9cbedad77@HE1EUR01FT006.eop-EUR01.prod.protection.outlook.com>
2021-01-18 10:26 ` Stephane Viau [this message]
2021-01-18 17:30 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-01-15 Yann E. MORIN
2021-01-19 5:52 ` Stephane Viau
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=PA4PR04MB7920C4990EEA59953B4C3C4DA7A40@PA4PR04MB7920.eurprd04.prod.outlook.com \
--to=stephane.viau@oss.nxp.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 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.