From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
Date: Mon, 26 Mar 2018 13:55:34 +0200 [thread overview]
Message-ID: <a263d2ff-b184-e199-629c-e523ba026a02@mind.be> (raw)
In-Reply-To: <20180325212036.06226774@windsurf>
On 25-03-18 21:20, Thomas Petazzoni wrote:
> Hello,
>
> On Sat, 24 Mar 2018 20:15:33 -0500, Matthew Weber wrote:
>
>>> Fixes:
>>>
>>> https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355
>>
>> Sorry, I didn't realize this failed. Is there an automated email on
>> this sort of failure?
>
> No, there isn't. Unfortunately, the Gitlab CI infra is not very
> reliable, and a number of failures are not related to real problems in
> Buildroot, but to Gitlab CI infrastructure problems.
Well, to be completely fair, it's not really the Gitlab CI infra which is
unreliable. Rather, it's the free runners that are unreliable. I expect that if
we would have a dedicated runner, we wouldn't see these problems. At least,
that's how it looks to me (I'm not really an expert though).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2018-03-26 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 14:26 [Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build Thomas Petazzoni
2018-03-24 17:31 ` Peter Korsgaard
2018-03-25 1:15 ` Matthew Weber
2018-03-25 19:20 ` Thomas Petazzoni
2018-03-26 11:55 ` Arnout Vandecappelle [this message]
2018-03-26 12:46 ` Matthew Weber
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=a263d2ff-b184-e199-629c-e523ba026a02@mind.be \
--to=arnout@mind.be \
--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