From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-23
Date: Fri, 24 Feb 2017 14:12:45 +0100 [thread overview]
Message-ID: <20170224141245.71bf2eb5@free-electrons.com> (raw)
In-Reply-To: <901801527.12088604.1487934060090.JavaMail.zimbra@datacom.ind.br>
Hello,
On Fri, 24 Feb 2017 08:01:00 -0300 (BRT), Carlos Santos wrote:
> > Build statistics for 2017-02-23
> [...]
> > host-util-linux-2.29.2 | 1
>
> ERROR: certificate common name `k.ssl.fastly.net' doesn't match requested host name `cdn.kernel.org'.
This gets automatically solved by sources.buildroot.net caching the
tarball. However, since I agree that it happens quite regularly,
perhaps we could add some logic in autobuild-run to detect such build
failures and ignore them?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-24 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-23 Thomas Petazzoni
2017-02-24 11:01 ` Carlos Santos
2017-02-24 13:12 ` Thomas Petazzoni [this message]
2017-02-24 15:41 ` Arnout Vandecappelle
2017-02-24 15:46 ` Thomas Petazzoni
2017-02-24 16:48 ` Arnout Vandecappelle
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=20170224141245.71bf2eb5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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