Architecture build statistics
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
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
Quoted 39 lines · Thomas Petazzoni
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
Dear Chris Zankel,
Quoted 1 line · Chris Zankel
Great statistics. Xtensa definitely needs some work here ;-)
It seems yes :-)
Are you interested in receiving a daily e-mail with the Xtensa build failures, if any?
Quoted 1 line
I looked into the failures a while ago and started to create patches.
Please submit them, then :)
Quoted 3 lines
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 :-)
Unfortunately, seeing the absolute desert of release activity the uClibc project is showing, I am not sure when any feature of this size can be merged, and even worse released :-(
In the mean time, it would be good if we could identify such packages, and add the appropriate dependencies to avoid autobuilder failures. Can you point us which packages need NPTL support?
For the record, the 10 packages causing the highest number of problems since July, 1st 2013, are:
+-------------------+-----+ | reason | cnt | +-------------------+-----+ | binutils-2.21.1 | 96 | | m4-1.4.16 | 37 | | binutils-2.22 | 30 | | libnspr-4.9.6 | 21 | | m4-1.4.17 | 17 | | cdrkit-1.1.11 | 14 | | ffmpeg-0.8.12 | 8 | | iozone-3_414 | 8 | | gstreamer-0.10.36 | 6 | | libpfm4-4.3.0 | 6 | +-------------------+-----+
Looks like fixing binutils is a good thing to do in the very near future. Can you send a patch for that?
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Quoted 2 lines · Thomas Petazzoni
Are you interested in receiving a daily e-mail with the Xtensa build failures, if any?
Are they different from the one on the mailing list?
For example:
[Buildroot] [autobuild.buildroot.net] Build results for 2013-10-28
Quoted 3 lines
Unfortunately, seeing the absolute desert of release activity the uClibc project is showing, I am not sure when any feature of this size can be merged, and even worse released :-(
Hopefully, I can push them to make a 'pre-release'.
Quoted 3 lines
In the mean time, it would be good if we could identify such packages, and add the appropriate dependencies to avoid autobuilder failures. Can you point us which packages need NPTL support?
I'll go through my list again, and will run some builds. Give me a few days to a week to come up with a list and patches...
Quoted 19 lines
For the record, the 10 packages causing the highest number of problems since July, 1st 2013, are:
+-------------------+-----+ | reason | cnt | +-------------------+-----+ | binutils-2.21.1 | 96 | | m4-1.4.16 | 37 | | binutils-2.22 | 30 | | libnspr-4.9.6 | 21 | | m4-1.4.17 | 17 | | cdrkit-1.1.11 | 14 | | ffmpeg-0.8.12 | 8 | | iozone-3_414 | 8 | | gstreamer-0.10.36 | 6 | | libpfm4-4.3.0 | 6 | +-------------------+-----+
Quoted 2 lines
Looks like fixing binutils is a good thing to do in the very near future. Can you send a patch for that?
Actually, when you run automatic builds, do you 'cache' the dl directory? What I noticed is that 'snapshots' of packages are not (were not) updated (probably because the filename doesn't change). If cached, it would be good to delete all 'snapshot' from the dl directory (short term solution). I'll see if I can come up with a solution to 'pin' a working version for uClibc for Xtensa.
Some of the binutils errors might come from using 'uClibc' snapshots, and if the uClibc-snapshot package is not cleared, the same error will continue to show up even if fixed.
Thanks,
-Chris
Dear Chris Zankel,
Quoted 7 lines · Chris Zankel
Quoted 2 lines · Thomas Petazzoni
Are you interested in receiving a daily e-mail with the Xtensa build failures, if any?
Are they different from the one on the mailing list?
For example:
[Buildroot] [autobuild.buildroot.net] Build results for 2013-10-28
They are different only in the sense that they contain the failures for only a given architecture, and they are sent to the architecture maintainer directly rather than to the list. This allows you to look only at "your" failures rather than the entire set of failures, and ensure that you see the e-mail even if you don't read the entire mailing list traffic.
Quoted 4 lines
Quoted 3 lines
Unfortunately, seeing the absolute desert of release activity the uClibc project is showing, I am not sure when any feature of this size can be merged, and even worse released :-(
Hopefully, I can push them to make a 'pre-release'.
Cool!
Quoted 5 lines
Quoted 3 lines
In the mean time, it would be good if we could identify such packages, and add the appropriate dependencies to avoid autobuilder failures. Can you point us which packages need NPTL support?
I'll go through my list again, and will run some builds. Give me a few days to a week to come up with a list and patches...
Ok, thanks!
Quoted 27 lines
Quoted 18 lines
For the record, the 10 packages causing the highest number of problems since July, 1st 2013, are:
+-------------------+-----+ | reason | cnt | +-------------------+-----+ | binutils-2.21.1 | 96 | | m4-1.4.16 | 37 | | binutils-2.22 | 30 | | libnspr-4.9.6 | 21 | | m4-1.4.17 | 17 | | cdrkit-1.1.11 | 14 | | ffmpeg-0.8.12 | 8 | | iozone-3_414 | 8 | | gstreamer-0.10.36 | 6 | | libpfm4-4.3.0 | 6 | +-------------------+-----+Quoted 2 lines
Looks like fixing binutils is a good thing to do in the very near future. Can you send a patch for that?
Actually, when you run automatic builds, do you 'cache' the dl directory? What I noticed is that 'snapshots' of packages are not (were not) updated (probably because the filename doesn't change). If cached, it would be good to delete all 'snapshot' from the dl directory (short term solution). I'll see if I can come up with a solution to 'pin' a working version for uClibc for Xtensa.
Quoted 3 lines
Some of the binutils errors might come from using 'uClibc' snapshots, and if the uClibc-snapshot package is not cleared, the same error will continue to show up even if fixed.
The autobuilders indeed have a download cache. However, they randomly remove 5 tarballs from the download cache after each build, to ensure we regularly re-download tarballs from their upstream location, which allows to check that we have it correct in BR.
At the time of this writing, the uClibc-snapshot.tar.bz2 is present in two of the autobuilders instances, and the date is quite recent:
$ find 1/dl/ 2/dl/ 3/dl/ -name 'uClibc-snapshot.tar.bz2' | xargs ls -l -rw-r--r-- 1 thomas thomas 2857900 Oct 29 01:10 1/dl/uClibc-snapshot.tar.bz2 -rw-r--r-- 1 thomas thomas 2857900 Oct 26 02:10 2/dl/uClibc-snapshot.tar.bz2
However, it's true that some of the builds may have been done with older uClibc snapshots. Using uClibc-snapshot.tar.bz2 is really not great since it doesn't guarantee the reproducibility of builds. Unfortunately, they only keep one month of snapshots at
http://uclibc.org/downloads/snapshots/ so that's not really usable for our purpose.
The only option that I can see is to introduce fake 'uClibc-xtensa' version, which downloads a specific git commit. This way, we are sure to have the same version between builds, and you can update this version by sending a patch to Buildroot whenever needed.
Thoughts?
Thanks,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Hi Thomas,
Thanks for all the comments and explanation.
Quoted 4 lines · Thomas Petazzoni
Dear Chris Zankel,
Quoted 1 line · Chris Zankel
On 10/29/13, 1:16 PM, Thomas Petazzoni wrote:
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
Are you interested in receiving a daily e-mail with the Xtensa build failures, if any?
They are different only in the sense that they contain the failures for only a given architecture, and they are sent to the architecture maintainer directly rather than to the list. This allows you to look only at "your" failures rather than the entire set of failures, and ensure that you see the e-mail even if you don't read the entire mailing list traffic.
Great! Sign me up then :-)
Quoted 6 lines
The only option that I can see is to introduce fake 'uClibc-xtensa' version, which downloads a specific git commit. This way, we are sure to have the same version between builds, and you can update this version by sending a patch to Buildroot whenever needed.
Thoughts?
Sounds like a plan. Give me a few days, though, a lot going on right now.
Thanks,
-Chris
Hi Thomas,
Just a quick update on binutils. There seems to be an issue with uClibc (_obstack_* symbols are not exported). I also tried a similar build for ARM with the same result (same error). Do you have any test builds using a uClibc snapshot for other architectures that pass binutils?
There was a discussion about it on the uClibc mailing list a while ago.
Thanks,
-Chris
Quoted 20 lines · Thomas Petazzoni
For the record, the 10 packages causing the highest number of problems since July, 1st 2013, are:
+-------------------+-----+ | reason | cnt | +-------------------+-----+ | binutils-2.21.1 | 96 | | m4-1.4.16 | 37 | | binutils-2.22 | 30 | | libnspr-4.9.6 | 21 | | m4-1.4.17 | 17 | | cdrkit-1.1.11 | 14 | | ffmpeg-0.8.12 | 8 | | iozone-3_414 | 8 | | gstreamer-0.10.36 | 6 | | libpfm4-4.3.0 | 6 | +-------------------+-----+Looks like fixing binutils is a good thing to do in the very near future. Can you send a patch for that?
Hi Thomas,
Quoted 4 lines
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 for the list of results. Quite a few of the failures are related to some bugs in our version of GCC. We have fixed a number of these bugs and will release a new version of the toolchain soon (coming week?). With this release, I will also submit patches to the Buildroot project so that the latest TAR will be used.
Mischa
Dear Mischa Jonker,
Quoted 11 lines · Mischa Jonker
Quoted 5 lines
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 for the list of results. Quite a few of the failures are related to some bugs in our version of GCC. We have fixed a number of these bugs and will release a new version of the toolchain soon (coming week?). With this release, I will also submit patches to the Buildroot project so that the latest TAR will be used.
Excellent, thanks, looking forward to see these changes.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Hi all, hi Thomas
This is kind of an apology, for I am yet to review those few errors compiling openssl for microblaze you noticed a couple of weeks ago.
I can currently spend about a 10% of my paid time to make sure the software we code at our compay is cross platform and for that I use buildroot. Little by little, I will be facing those bugs (specifically for arm, powerpc microblaze, and maybe x86_64 and i686) and also will encounter the need to build some new packages (such as libxmlrpc I sent a few days ago).
I can't promise any specific amount of direct effort to solve any specific issue, but I just want you all to know that I keep them in mind and will try to help out with them during the little time I can dedicate to buildroot.
Hopefully, some of those bugs will be blocking my cross porting work and then I'll be able to explain my boss why I spent my time solving them. I wish I could spend more time to buildroot outside job, but for now that'll be it.
Thank you all, regards
2013/10/29 Thomas Petazzoni <[email protected]>
Quoted 44 lines
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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
Signature · 4 lines
?lvaro G?mez Machado -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131029/ad1590fa/attachment.html>
Quoted 9 lines · Thomas Petazzoni
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) :
Quoted 6 lines
+------------+---------+----------+-------+------------+------------+ | 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?
Signature · 3 lines
Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com
Dear Ezequiel Garcia,
Quoted 10 lines · Ezequiel Garcia
Quoted 6 lines
+------------+---------+----------+-------+------------+------------+ | 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.
Internal toolchain is never used for nios2:
config BR2_TOOLCHAIN_BUILDROOT
bool "Buildroot toolchain"
- depends on !BR2_microblaze && !BR2_aarch64
+ depends on !BR2_microblaze && !BR2_aarch64 && !BR2_nios2
this was in 830205c0361c751c39fabeb1366100e2a94a27a4, which comes from you :-)
Indeed most of the issues are caused by the lack of libffi support:
+--------------------------+-----+ | reason | cnt | +--------------------------+-----+ | libffi-3.0.13 | 28 | | aiccu-20070115 | 10 | | binutils-2.21 | 9 | | libnspr-4.9.6 | 1 | | e2fsprogs-1.42.8 | 1 | | libnetfilter_queue-1.0.2 | 1 | +--------------------------+-----+
but there's also a bunch of other problems as you can see. For the time being, I've modified the autobuilders script to avoid any configuration that involves libffi on nios2. Since the nios2 support in libffi has recently been contributed, they will hopefully make a new release in the near future.
Quoted 3 lines
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?
It wasn't implemented until I received your e-mail, but it's now done. Enjoy:
http://autobuild.buildroot.org/?arch=nios2
http://autobuild.buildroot.org/?arch=nios2&status=OK
http://autobuild.buildroot.org/?arch=nios2&status=NOK
See:
http://git.buildroot.net/buildroot-test/commit/?id=4840eec19648172b6fc9e83fe2c2f1dea550c1cf
http://git.buildroot.net/buildroot-test/commit/?id=823c2408414899a6b4fc82bc409eb14e76fefa48
Quoted 2 lines
Maybe this would help arch-maintainers to focus in what's relevant for them?
Hopefully :-)
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Quoted 22 lines · Thomas Petazzoni
Dear Ezequiel Garcia,
Quoted 10 lines · Ezequiel Garcia
Quoted 6 lines
+------------+---------+----------+-------+------------+------------+ | 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.
Internal toolchain is never used for nios2:
config
BR2_TOOLCHAIN_BUILDROOT
bool "Buildroot toolchain"(quoted diff) +1
-1- depends on !BR2_microblaze && !BR2_aarch64 + depends on !BR2_microblaze && !BR2_aarch64 && !BR2_nios2
Quoted 3 lines
this was in
830205c0361c751c39fabeb1366100e2a94a27a4, which comes from you :-)
:)
Quoted 13 lines
Indeed most of the issues are caused by the lack of libffi support:
+--------------------------+-----+ | reason | cnt | +--------------------------+-----+ | libffi-3.0.13 | 28 | | aiccu-20070115 | 10 | | binutils-2.21 | 9 | | libnspr-4.9.6 | 1 | | e2fsprogs-1.42.8 | 1 | | libnetfilter_queue-1.0.2 | 1 | +--------------------------+-----+
Quoted 1 line
but there's also a bunch of other problems as you can see.
Yup. Let me take a look...
Quoted 7 lines
Quoted 3 lines
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?
It wasn't implemented until I received your e-mail, but it's now done. Enjoy:
Quoted 9 lines
http://autobuild.buildroot.org/?arch=nios2
http://autobuild.buildroot.org/?arch=nios2&status=OK
http://autobuild.buildroot.org/?arch=nios2&status=NOKSee:
http://git.buildroot.net/buildroot-test/commit/?id=4840eec19648172b6fc9e83fe2c2f1dea550c1cf http://git.buildroot.net/buildroot-test/commit/?id=823c2408414899a6b4fc82bc409eb14e76fefa48
Awesome! You can add my:
Signature · 3 lines
Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com
Hi Thomas,
Quoted 10 lines · Thomas Petazzoni
Quoted 3 lines
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?
It wasn't implemented until I received your e-mail, but it's now done. Enjoy:
http://autobuild.buildroot.org/?arch=nios2
http://autobuild.buildroot.org/?arch=nios2&status=OK
http://autobuild.buildroot.org/?arch=nios2&status=NOK
Great!
It seems that filtering by architecture does not work for x86_64. The following URL displays build statuses of all architectures, not only x86_64:
http://autobuild.buildroot.org/?arch=x86_64
Best regards,
Signature · 1 line
Christophe Vu-Brugier
Dear Christophe Vu-Brugier,
Quoted 7 lines · Christophe Vu-Brugier
Quoted 6 lines
It wasn't implemented until I received your e-mail, but it's now done. Enjoy:
http://autobuild.buildroot.org/?arch=nios2
http://autobuild.buildroot.org/?arch=nios2&status=OK
http://autobuild.buildroot.org/?arch=nios2&status=NOK
Quoted 7 lines
Great!
It seems that filtering by architecture does not work for
x86_64. The following URL displays build statuses of all architectures, not onlyx86_64:
Thanks for noticing. I've fixed that now, by committing:
http://git.buildroot.net/buildroot-test/commit/?id=2a0407cbe338bd5823014a860325fa31a3a90378
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
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.
Quoted 4 lines · Thomas Petazzoni
+------------+---------+----------+-------+------------+------------+ | 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.
Quoted 1 line
| microblaze | 6 | 308 | 314 | 1.9108 | 98.0892 |
E-mail sent to Spenser Gilliland.
Quoted 1 line
| nios2 | 2 | 49 | 51 | 3.9216 | 96.0784 |
E-mail sent to Ezequiel Garcia.
Quoted 1 line
| xtensa | 13 | 314 | 327 | 3.9755 | 96.0245 |
E-mail sent to Chris Zankel.
Quoted 1 line
| avr32 | 34 | 305 | 339 | 10.0295 | 89.9705 |
E-mail sent to Simon Dawson.
Quoted 1 line
| mips64el | 162 | 498 | 660 | 24.5455 | 75.4545 |
E-mail sent to Markos Chandras, from Imagination Technologies.
Quoted 1 line
| aarch64 | 82 | 243 | 325 | 25.2308 | 74.7692 |
No specific maintainer (I'm mainly taking care of aarch64 issues)
Quoted 1 line
| arc | 95 | 234 | 329 | 28.8754 | 71.1246 |
E-mail sent to Mischa Jonker, from Synopsis.
Quoted 1 line
| sh4a | 158 | 171 | 330 | 47.8788 | 51.8182 |
No specific maintainer. Who anyone be interested?
Quoted 1 line
| mipsel | 172 | 168 | 340 | 50.5882 | 49.4118 |
E-mail sent to Markos Chandras, from Imagination Technologies.
Quoted 1 line
| mips | 172 | 165 | 337 | 51.0386 | 48.9614 |
E-mail sent to Markos Chandras, from Imagination Technologies.
Quoted 5 lines
| 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 |
No specific maintainers for these architectures.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Quoted 48 lines · Thomas Petazzoni
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.
Quoted 4 lines · Thomas Petazzoni
+------------+---------+----------+-------+------------+------------+ | 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.
Quoted 1 line
| microblaze | 6 | 308 | 314 | 1.9108 | 98.0892 |
E-mail sent to Spenser Gilliland.
Quoted 1 line
| nios2 | 2 | 49 | 51 | 3.9216 | 96.0784 |
E-mail sent to Ezequiel Garcia.
Quoted 1 line
| xtensa | 13 | 314 | 327 | 3.9755 | 96.0245 |
E-mail sent to Chris Zankel.
Quoted 1 line
| avr32 | 34 | 305 | 339 | 10.0295 | 89.9705 |
E-mail sent to Simon Dawson.
Quoted 1 line
| mips64el | 162 | 498 | 660 | 24.5455 | 75.4545 |
E-mail sent to Markos Chandras, from Imagination Technologies.
Quoted 1 line
| aarch64 | 82 | 243 | 325 | 25.2308 | 74.7692 |
No specific maintainer (I'm mainly taking care of aarch64 issues)
Quoted 1 line
| arc | 95 | 234 | 329 | 28.8754 | 71.1246 |
E-mail sent to Mischa Jonker, from Synopsis.
Quoted 1 line
| sh4a | 158 | 171 | 330 | 47.8788 | 51.8182 |
No specific maintainer. Who anyone be interested?
Quoted 10 lines
Quoted 1 line
| mipsel | 172 | 168 | 340 | 50.5882 | 49.4118 |
E-mail sent to Markos Chandras, from Imagination Technologies.
Quoted 1 line
| mips | 172 | 165 | 337 | 51.0386 | 48.9614 |
E-mail sent to Markos Chandras, from Imagination Technologies.
Quoted 2 lines
| 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
Quoted 8 lines
Quoted 3 lines
| 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
Dear Sinan Akman,
Quoted 3 lines · Sinan Akman
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.
Sure. I know Gustavo also has a number of PowerPC platforms. Feel free to pick some PowerPC related issues in the autobuilder results and send fixes for them.
Here is the list of packages that were causing the highest number of problems on PowerPC since October, 1st 2013. Note that looking at the trace-cmd problem is useless, we already have a fix for this one (it just hasn't been applied to Buildroot yet), and that some of the problems below may have already been fixed, or may not necessarily be related to PowerPC specific issues.
+--------------------------------------------+-----+ | reason | cnt | +--------------------------------------------+-----+ | trace-cmd-trace-cmd-v2.2.1 | 219 | | host-util-linux-2.23.2 | 41 | | gstreamer-0.10.36 | 33 | | php-5.3.27 | 18 | | make: *** [uboot-tools-legal-info] Error 1 | 16 | | w_scan-20130331 | 16 | | bison-3.0 | 14 | | nano-2.3.2 | 11 | | omniorb-4.1.6 | 10 | | mpd-0.17.6 | 10 | | cryptsetup-1.6.2 | 10 | | webkit-1.11.5 | 8 | | qt-4.8.5 | 8 | | minidlna-1.0.26 | 7 | | mediastreamer-2.8.2 | 6 | | rpm-5.2.0 | 6 | | uboot-tools-2013.10 | 6 | | binutils-2.21 | 5 | | alsa-lib-1.0.26 | 4 | | qt5base-5.1.1 | 4 | | gst1-plugins-bad-1.2.0 | 4 | | nettle-2.7.1 | 3 | | uclibc-0.9.33.2 | 3 | | host-uboot-tools-2013.10 | 3 | | enlightenment-0.17.3 | 3 | | sysklogd-1.5 | 2 | | imagemagick-6.8.6-2 | 2 | | audiofile-0.3.6 | 2 | | alsa-utils-1.0.26 | 2 | | python-2.7.3 | 2 | | gettext-0.18.3.1 | 2 | | mediastreamer-2.9.0 | 2 | | host-cmake-2.8.10.2 | 2 | | cairo-1.12.10 | 1 | | matchbox-keyboard-0.1 | 1 | | cdrkit-1.1.11 | 1 | | fltk-1.1.7 | 1 | | imagemagick-6.8.7-0 | 1 | | libargtable2-13 | 1 | | make: write error | 1 | | libwebsockets-v1.22-chrome26-firefox18 | 1 | | host-expat-2.1.0 | 1 | | host-gettext-0.18.3.1 | 1 | | dbus-1.4.26 | 1 | | weston-1.1.0 | 1 | | protobuf-2.4.1 | 1 | | httping-2.2.1 | 1 | | mtdev2tuio-e1e7378 | 1 | | systemd-44 | 1 | | libcgroup-0.38 | 1 | | host-ruby-1.9.3-p448 | 1 | | tn5250-0.17.4 | 1 | | netsnmp-5.7.2 | 1 | | usbredir-0.6 | 1 | | udisks-1.0.4 | 1 | | libsvgtiny-12121 | 1 | | bustle-0.4.2 | 1 | | host-libglib2-2.36.3 | 1 | | host-protobuf-c-0.15 | 1 | | libiconv-1.14 | 1 | | xlib_libpthread-stubs-0.3 | 1 | | collectd-5.4.0 | 1 | | qt5webkit-5.0.2 | 1 | | pcsc-lite-1.8.6 | 1 | +--------------------------------------------+-----+
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Quoted 5 lines · Thomas Petazzoni
Dear Sinan Akman,
[...]
Sure. I know Gustavo also has a number of PowerPC platforms. Feel free to pick some PowerPC related issues in the autobuilder results and send fixes for them.
Will do and at any point if you find appropriate feel free to
assign me as a maintainer if no one else is interested in. I will then see how much time I can put aside to work on this regularly.
Regards
Sinan Akman
buildroot-bounces at busybox.net wrote on 11/02/2013 05:05:29 AM:
Quoted 12 lines
From: Thomas Petazzoni <[email protected]>
To: Sinan Akman <[email protected]>
Cc: "Zhang, Sonic" <[email protected]>, chrisgriffith at cox.net, Jan Viktorin <[email protected]>, buildroot at uclibc.org, Mischa Jonker <[email protected]>, Spenser Gilliland <[email protected]>
Date: 11/02/2013 05:05 AM
Subject: Re: [Buildroot] Architecture build statistics
Sent by: buildroot-bounces at busybox.netDear Sinan Akman,
<snip>
Quoted 13 lines
+--------------------------------------------+-----+ | reason | cnt | +--------------------------------------------+-----+ | trace-cmd-trace-cmd-v2.2.1 | 219 | | host-util-linux-2.23.2 | 41 | | gstreamer-0.10.36 | 33 | | php-5.3.27 | 18 | | make: *** [uboot-tools-legal-info] Error 1 | 16 | | w_scan-20130331 | 16 | | bison-3.0 | 14 | | nano-2.3.2 | 11 | | omniorb-4.1.6 | 10 |
A patch has been submitted to fix omniorb.
(Oct 21st, "omniorb: fix autobuilder failure")
Quoted 2 lines
| mpd-0.17.6 | 10 | | cryptsetup-1.6.2 | 10 |
<snip>
Thanks!
Matt Weber
mlweber1 at rockwellcollins.com
Thomas et al.
Quoted 5 lines · Thomas Petazzoni
Quoted 2 lines
| nios2 | 2 | 49 | 51 | 3.9216 | 96.0784 |
E-mail sent to Ezequiel Garcia.
Thanks! I'm already looking at them :-)
I've been doing some experiments and I expect *lots* of broken packages. Unfortunately, these breaks are either related to nios2 being an unsupported arch (e.g. ltrace, strace) or some toolchain issues (e.g. Qt).
I'd like to take care of this, but as you can imagine, these are pretty challenging problems.
And to make things worse, nios2 Linux port is not mainlined and it looks a bit rusty.
On the other side, I have a few boards to run this, and I'm using BR on them, so I'm more than willing to support this.
Signature · 2 lines
Ezequiel Garc?a, VanguardiaSur www.vanguardiasur.com.ar
Dear Ezequiel Garc?a,
Quoted 1 line · Ezequiel Garc?a
Thanks! I'm already looking at them :-)
Great!
Quoted 7 lines
I've been doing some experiments and I expect *lots* of broken packages. Unfortunately, these breaks are either related to nios2 being an unsupported arch (e.g. ltrace, strace) or some toolchain issues (e.g. Qt).
I'd like to take care of this, but as you can imagine, these are pretty challenging problems.
Note that we don't need to support everything on all platforms. If some package doesn't have support for NIOS 2, then we can simply add a 'depends on !BR2_nios2' to it.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com