Hi there. I've created a new mailing list for the automated build results of Linaro GCC, Linaro GDB, and (once-weekly) FSF 4.5 and 4.6.
You can subscribe by going to: https://launchpad.net/~linaro-toolchain-builds
I've subscribed everyone in the toolchain working group. If you'd like to get these emails, go to: https://launchpad.net/people/+me/+editemails
and set 'Linaro Toolchain Builds' to 'Preferred address'. Any build failures will also go to linaro-toolchain@l.linaro.org.
The archive is here: https://lists.launchpad.net/linaro-toolchain-builds/
You can also track the crude state of the build hosts here: http://ex.seabright.co.nz/helpers/scheduler
and see things status scroll by on #linaro-cbuild on Freenode.
This was kicked off due to the problems with the 2011.01 release. The follow-up is tracked here: https://blueprints.launchpad.net/gcc-linaro/+spec/incident-followup-1
-- Michael
On Friday, February 18, 2011 2:17:38 am Michael Hope wrote:
Hi there. I've created a new mailing list for the automated build results of Linaro GCC, Linaro GDB, and (once-weekly) FSF 4.5 and 4.6.
Interesting! Thanks for setting this up. Do we want to send the results of the weekly FSF builds to the (gdb|gcc)-testresults mailing lists? The source tree contains a script that extracts the fails and generates a mail from the *.log files: src/contrib/test_summary -t > testresults
Regards Ken
On Sat, Feb 19, 2011 at 2:32 AM, Ken Werner ken@linux.vnet.ibm.com wrote:
Good spotting. I've been planning to do this for a while but keep getting distracted. The plan is to send FSF 4.5, FSF trunk, and Linaro 4.5 and 4.6 results up to gcc-testresults@.
-- Michael
linaro-toolchain@lists.linaro.org
-
Ken Werner -
Michael Hope