From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-02-09
Date: Wed, 11 Feb 2015 07:02:18 +0100 [thread overview]
Message-ID: <20150211070218.4f7ab59b@free-electrons.com> (raw)
In-Reply-To: <87siee18ip.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Tue, 10 Feb 2015 09:21:50 +0100, Peter Korsgaard wrote:
> > mipsel | strace-4.9 | NOK | http://autobuild.buildroot.net/results/d3f123367559c758649c6da0ee4df528cb2d4682/
> > mipsel | strace-4.9 | NOK | http://autobuild.buildroot.net/results/cd713c2513cd1eb39b657504203338c4b7f5c887/
> > mipsel | strace-4.9 | NOK | http://autobuild.buildroot.net/results/0220ecb696a742641b83949f187d2d74e442f48a/
>
> Didn't we already blacklist those uClibc/MIPS toolchains?
Yes, but the script isn't necessarily up-to-date on all the autobuilder
instances. I updated it on my instance yesterday, I should probably
send a notification to all people running autobuilder instances.
It's an issue we discussed at the Buildroot meeting, but there's no
simple way to handle this problem, without making the script update
itself, which isn't that nice from a security PoV since it means I
could be pushing whatever code I want to all the autobuilder instances,
without the owner of those instances noticing.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-02-11 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-02-09 Thomas Petazzoni
2015-02-10 8:21 ` Peter Korsgaard
2015-02-11 6:02 ` Thomas Petazzoni [this message]
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=20150211070218.4f7ab59b@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