From: Sinan Akman <sinan@writeme.com>
To: buildroot@busybox.net
Subject: [Buildroot] Architecture build statistics
Date: Sat, 02 Nov 2013 02:31:48 -0400 [thread overview]
Message-ID: <52749C54.8080601@writeme.com> (raw)
In-Reply-To: <20131101193153.04cdd643@skate>
On 11/01/2013 02:31 PM, Thomas Petazzoni wrote:
> Hello all,
>
> Following to this e-mail, I've just added a bunch of architecture
> "maintainers" that will receive each day an e-mail with list of the
> build failures related to the architecture they take care of in
> Buildroot. See below for the detail.
>
> On Tue, 29 Oct 2013 20:41:08 +0100, Thomas Petazzoni wrote:
>
>> +------------+---------+----------+-------+------------+------------+
>> | arch | success | failures | total | pctsuccess | pctfailure |
>> +------------+---------+----------+-------+------------+------------+
>> | bfin | 10 | 607 | 617 | 1.6207 | 98.3793 |
>
> E-mail sent to Aaron Wu and Sonic Zhang from Analog Devices.
>
>> | microblaze | 6 | 308 | 314 | 1.9108 | 98.0892 |
>
> E-mail sent to Spenser Gilliland.
>
>> | nios2 | 2 | 49 | 51 | 3.9216 | 96.0784 |
>
> E-mail sent to Ezequiel Garcia.
>
>> | xtensa | 13 | 314 | 327 | 3.9755 | 96.0245 |
>
> E-mail sent to Chris Zankel.
>
>> | avr32 | 34 | 305 | 339 | 10.0295 | 89.9705 |
>
> E-mail sent to Simon Dawson.
>
>> | mips64el | 162 | 498 | 660 | 24.5455 | 75.4545 |
>
> E-mail sent to Markos Chandras, from Imagination Technologies.
>
>> | aarch64 | 82 | 243 | 325 | 25.2308 | 74.7692 |
>
> No specific maintainer (I'm mainly taking care of aarch64 issues)
>
>> | arc | 95 | 234 | 329 | 28.8754 | 71.1246 |
>
> E-mail sent to Mischa Jonker, from Synopsis.
>
>> | sh4a | 158 | 171 | 330 | 47.8788 | 51.8182 |
>
> No specific maintainer. Who anyone be interested?
>
>> | mipsel | 172 | 168 | 340 | 50.5882 | 49.4118 |
>
> E-mail sent to Markos Chandras, from Imagination Technologies.
>
>> | mips | 172 | 165 | 337 | 51.0386 | 48.9614 |
>
> E-mail sent to Markos Chandras, from Imagination Technologies.
>
>> | arm | 2302 | 1788 | 4097 | 56.1875 | 43.6417 |
>> | powerpc | 2794 | 1616 | 4411 | 63.3416 | 36.6357 |
Hi Thomas
I don't know if I would qualify well as a maintainer but
I have quite a number of powerpc boards that I build and use
buildroot almost regularly.
Let me know if this can be of any help.
Regards
Sinan Akman
>> | 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 |
>
> No specific maintainers for these architectures.
>
> Thomas
>
next prev parent reply other threads:[~2013-11-02 6:31 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
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 [this message]
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=52749C54.8080601@writeme.com \
--to=sinan@writeme.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