From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2015-06-04
Date: Tue, 9 Jun 2015 08:52:19 +0000 [thread overview]
Message-ID: <1433839938.3732.5.camel@synopsys.com> (raw)
In-Reply-To: <20150605063013.14562100B13@stock.ovh.net>
Hi Thomas,
On Fri, 2015-06-05 at 08:30 +0200, Thomas Petazzoni wrote:
> Those results are limited to the arc architecture.
>
> Build statistics for 2015-06-04
> ===============================
>
> success : 14
> failures : 1
> timeouts : 0
> TOTAL : 15
>
> Classification of failures by reason
> ====================================
>
> ntfs-3g-2015.3.14 | 1
>
> Detail of failures
> ===================
>
> arc | ntfs-3g-2015.3.14 | NOK | http://autobuil
> d.buildroot.net/results/7227d5f01755affa2a234eedd8d1fc8c826395c7/
>
Looks like Peter already fixed this in http://git.buildroot.net/buildro
ot/commit/package/ntfs-3g?id=174b8469029cb8018200516a00a5b890ec7cd1a8
-Alexey
parent reply other threads:[~2015-06-09 8:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20150605063013.14562100B13@stock.ovh.net>]
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=1433839938.3732.5.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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