From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-05-19
Date: Thu, 21 May 2015 08:55:48 +0200 [thread overview]
Message-ID: <1432191348.12102.1.camel@embedded.rocks> (raw)
In-Reply-To: <20150520231825.240a9292@free-electrons.com>
On Mi, 2015-05-20 at 23:18 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 20 May 2015 08:30:15 +0200 (CEST), Thomas Petazzoni wrote:
>
> > success : 317
> > failures : 14
> > timeouts : 2
> > TOTAL : 333
>
> So not as good as the day before, but let's have a look anyway.
>
> > Detail of failures
> > ===================
> >
> > arm | nodejs-0.10.38 | NOK | http://autobu
> > ild.buildroot.net/results/824bbeeeee5e04039bf9d7645a44f3f2aeca7628/
>
> Not sure what happened here:
>
> sh: echo: I/O error
>
> I think we should probably ignore?
I think so, too.
next prev parent reply other threads:[~2015-05-21 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-05-19 Thomas Petazzoni
2015-05-20 21:18 ` Thomas Petazzoni
2015-05-21 6:55 ` Jörg Krause [this message]
2015-05-26 7:11 ` Alexey Brodkin
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=1432191348.12102.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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