From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] Architecture build statistics
Date: Tue, 29 Oct 2013 13:11:46 -0700 [thread overview]
Message-ID: <52701682.2040208@zankel.net> (raw)
In-Reply-To: <20131029204108.5d707d09@skate>
Hi Thomas,
Great statistics. Xtensa definitely needs some work here ;-)
I looked into the failures a while ago and started to create patches.
However, one major issue was lacking NPTL support in uClibc. We are
currently working on it and are getting close to support it. This
already should push the pct columns higher :-)
Thanks,
-Chris
On 10/29/13, 12:41 PM, Thomas Petazzoni wrote:
> Hello all,
>
> 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 |
> | xtensa | 13 | 314 | 327 | 3.9755 | 96.0245 |
> | avr32 | 34 | 305 | 339 | 10.0295 | 89.9705 |
> | mips64el | 162 | 498 | 660 | 24.5455 | 75.4545 |
> | aarch64 | 82 | 243 | 325 | 25.2308 | 74.7692 |
> | arc | 95 | 234 | 329 | 28.8754 | 71.1246 |
> | sh4a | 158 | 171 | 330 | 47.8788 | 51.8182 |
> | mipsel | 172 | 168 | 340 | 50.5882 | 49.4118 |
> | mips | 172 | 165 | 337 | 51.0386 | 48.9614 |
> | arm | 2302 | 1788 | 4097 | 56.1875 | 43.6417 |
> | powerpc | 2794 | 1616 | 4411 | 63.3416 | 36.6357 |
> | sh4 | 208 | 120 | 328 | 63.4146 | 36.5854 |
> | x86_64 | 874 | 412 | 1288 | 67.8571 | 31.9876 |
> | i686 | 2369 | 572 | 2943 | 80.4961 | 19.4359 |
> +------------+---------+----------+-------+------------+------------+
>
> It would be really nice if the people working on those architectures in
> Buildroot could contribute a little bit more to fix the autobuilders
> failures, or at least get in touch with us to discuss how to solve
> them, or if they have no clue how to solve them.
>
> Thanks,
>
> Thomas
next prev parent reply other threads:[~2013-10-29 20:11 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 [this message]
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
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=52701682.2040208@zankel.net \
--to=chris@zankel.net \
--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