From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2016-05-31
Date: Wed, 1 Jun 2016 08:17:21 +0000 [thread overview]
Message-ID: <1464769003.3171.25.camel@synopsys.com> (raw)
In-Reply-To: <20160601063019.5D553101D2D@stock.ovh.net>
Hi Thomas,
On Wed, 2016-06-01 at 08:30 +0200, Thomas Petazzoni wrote:
> Those results are limited to the arc architecture.
>
> Build statistics for 2016-05-31
> ===============================
>
> ????????success : 14?
> ???????failures : 3??
> ???????timeouts : 0??
> ??????????TOTAL : 17?
>
> Classification of failures by reason
> ====================================
>
> ?????????????????mesa3d-11.2.2 | 2?
> ?????????????????jack2-v1.9.10 | 1?
>
> Detail of failures
> ===================
>
> ?????????arc |??????????????????jack2-v1.9.10 | NOK |
> http://autobuild.buildroot.net/results/c05e4a5280f34b2a1dff8a10adfd46f53344e13a/
So this one is almost fixed by Bernd but given he has no time for the real fix
we'll take a look at proposed solution and hopefully will cook up a patch ourselves.
> ?????????arc |??????????????????mesa3d-11.2.2 | NOK |
> http://autobuild.buildroot.net/results/6b29d2dc46a60d7b6aa442d2b2bad2795368bc81/
> ?????????arc |??????????????????mesa3d-11.2.2 | NOK | http://autobuild.buildroot.net/results/8212b9ca27ccd88004135feb2
> a96130d5906fc92/
This long-standing mesa3d problem is fixed with newer tools, so once "next" becomes
a new "master" issue will go away.
-Alexey
next parent reply other threads:[~2016-06-01 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160601063019.5D553101D2D@stock.ovh.net>
2016-06-01 8:17 ` Alexey Brodkin [this message]
2016-06-01 8:19 ` [Buildroot] [arc-buildroot] [autobuild.buildroot.net] arc build results for 2016-05-31 Thomas Petazzoni
2016-06-01 9:54 ` Alexey Brodkin
2016-06-01 11:40 ` 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=1464769003.3171.25.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