Hi Ramana. These are covered by the release process documentation but I thought I'd fill them out.
The builds are completing. You can see the finished grid at: http://ex.seabright.co.nz/helpers/buildlog/gcc-linaro-4.7-2012 Click on 'Compare' for each machine to see the results like: http://ex.seabright.co.nz/helpers/testcompare/gcc-linaro-4.7-2012.07/logs/armv7l-natty-cbuild342-tcpanda05-cortexa9r1/gcc-testsuite.txt The test compare picks a close version but falls back to something ancient. Add the correct previous version like: http://ex.seabright.co.nz/helpers/testcompare/gcc-linaro-4.7-2012.07/logs/armv7l-natty-cbuild342-tcpanda05-cortexa9r1/gcc-testsuite.txt?base=gcc-linaro-4.7-2012.06 Check for any differences by searching for 'Just in'. A is the previous release, B is this. There's one regression in http://ex.seabright.co.nz/helpers/testcompare/gcc-linaro-4.7-2012.07/logs/armv7l-natty-cbuild342-tcpanda06-armv5r2/gcc-testsuite.txt?base=gcc-linaro-4.7-2012.06 which is: gcc.target/arm/pr42172-1.c scan-assembler-times ldr 1 I'd normally check our upstream builds: http://ex.seabright.co.nz/helpers/buildlog/gcc-4.7+svn but this is a ARMv5 fault and we only track Cortex-A9. Checking gcc-testresults shows: http://gcc.gnu.org/ml/gcc-testresults/2012-07/msg00171.html so the fault is upstream. I've spawned the test-oecore-gcc-linaro-4.7-2012.07 / x86_64-heavy and ubutest-gcc-linaro-4.7-2012.07 / i686,x86_64 jobs. The results will pop up similar to the 4.6 ones in the buildlog. -- Michael _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
