From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Architecture build statistics
Date: Tue, 29 Oct 2013 20:41:04 -0300 [thread overview]
Message-ID: <20131029234103.GA2527@localhost> (raw)
In-Reply-To: <20131029204108.5d707d09@skate>
On Tue, Oct 29, 2013 at 08:41:08PM +0100, Thomas Petazzoni wrote:
>
> This e-mail is intentionally Cc'ed to a number of people who are
> working on specific architectures in Buildroot, and specifically the
> architectures having the highest number of problems in the autobuilders.
>
> I generated some statistics of the number of failed builds vs.
> successful builds since July, 1st 2013, and here are the results
> (ordered from the worst architecture to the best one) :
>
> +------------+---------+----------+-------+------------+------------+
> | arch | success | failures | total | pctsuccess | pctfailure |
> +------------+---------+----------+-------+------------+------------+
> | bfin | 10 | 607 | 617 | 1.6207 | 98.3793 |
> | microblaze | 6 | 308 | 314 | 1.9108 | 98.0892 |
> | nios2 | 2 | 49 | 51 | 3.9216 | 96.0784 |
Mind sharing what's breaking in nios2? If it's related to either libffi
or the internal toolchain, then we'll have to wait until proper support
is added upstream.
As a side note, wouldn't it be nice to have per-arch-filtering in the
autobuild status site? Going through the code quickly, I think it's just
a matter of adding a parameter to the SQL query, right?
Maybe this would help arch-maintainers to focus in what's relevant for
them?
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-29 23:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 19:41 [Buildroot] Architecture build statistics Thomas Petazzoni
2013-10-29 20:11 ` Chris Zankel
2013-10-29 20:16 ` Thomas Petazzoni
2013-10-29 20:52 ` Chris Zankel
2013-10-29 21:36 ` Thomas Petazzoni
2013-10-30 6:00 ` Chris Zankel
2013-11-05 18:36 ` Chris Zankel
2013-10-29 21:24 ` Mischa Jonker
2013-10-29 21:28 ` Thomas Petazzoni
2013-10-29 22:02 ` Alvaro Gamez
2013-10-29 23:41 ` Ezequiel Garcia [this message]
2013-10-30 0:12 ` Thomas Petazzoni
2013-10-30 0:27 ` Ezequiel Garcia
2013-10-30 8:14 ` Christophe Vu-Brugier
2013-10-30 8:29 ` Thomas Petazzoni
2013-11-01 18:31 ` Thomas Petazzoni
2013-11-02 6:31 ` Sinan Akman
2013-11-02 10:05 ` Thomas Petazzoni
2013-11-02 16:00 ` Sinan Akman
2013-11-04 13:54 ` Matthew Weber
2013-11-02 15:16 ` Ezequiel García
2013-11-02 15:24 ` Thomas Petazzoni
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=20131029234103.GA2527@localhost \
--to=ezequiel.garcia@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