From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Failed pipeline for 2021.02-rc1 | buildroot | 92237c45
Date: Thu, 11 Feb 2021 13:02:32 +0100 [thread overview]
Message-ID: <87blcqke1z.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <6594f32e-a013-2622-20a8-91cf6edf568a@essensium.com> (Arnout Vandecappelle's message of "Thu, 11 Feb 2021 08:36:54 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout.vandecappelle@essensium.com> writes:
> ?Hi all,
> ?I'm not sure to what extent you automatically get warned about these failures,
> so I'm forwarding this to you.
> ?2021.02-rc1 has been released, but 9 tests are failing on it. Could we get them
> fixed before the final release?
Thanks, I indeed don't receive such notifications.
> Job #1019385566 ( https://gitlab.com/buildroot.org/buildroot/-/jobs/1019385566/raw )
> Stage: test
> Name: avenger96_defconfig
Hmm, that log isn't very helpful. Any idea what is going on? I just did
a test build here without issues.
Is it perhaps a case of missing BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL?
--
Bye, Peter Korsgaard
next parent reply other threads:[~2021-02-11 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <602456474c4eb_b2ab5a703162be@gitlab-sidekiq-catchall-v1-6d55b89d66-6zn9h.mail>
[not found] ` <6594f32e-a013-2622-20a8-91cf6edf568a@essensium.com>
2021-02-11 12:02 ` Peter Korsgaard [this message]
2021-02-11 12:21 ` [Buildroot] Failed pipeline for 2021.02-rc1 | buildroot | 92237c45 Thomas Petazzoni
2021-02-11 12:29 ` Michael Walle
2021-02-11 12:49 ` Arnout Vandecappelle
2021-02-11 13:25 ` Thomas Petazzoni
2021-02-11 12:48 ` [Buildroot] Fwd: " Arnout Vandecappelle
2021-02-11 13:17 ` Peter Korsgaard
2021-02-11 19:52 ` Michael Walle
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=87blcqke1z.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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