search for: r241599

On 7 July 2015 at 06:17, Renato Golin <renato.golin at linaro.org> wrote: > ARM+AArch64 up. All gree. Just to note there was a bug in test-release.sh where the script would not exit if the build/tests failed making failures less noticeable. I've fixed it in r241599. It would be a good idea to use that fix unless you are happy combing through the logs for failures.

> Ben reports that he didn't get a tarball even after the rpath fix and > had to disable -o pipefail to get one. Still not sure what caused > this. 'make check' failures can cause this. I had to revert r241599 to get a package. > Appendix: compiler-rt test failures > =================================== > Just to add Mips to this: On big-endian Mips32r2: AddressSanitizer-mips-linux :: TestCases/Linux/kernel-area.cc AddressSanitizer-mips-linux :: TestCases/Posix/coverage-...

...el Sanders <Daniel.Sanders at imgtec.com> wrote: >> Ben reports that he didn't get a tarball even after the rpath fix and >> had to disable -o pipefail to get one. Still not sure what caused >> this. > > 'make check' failures can cause this. I had to revert r241599 to get a package. Oh, I'm silly. Some part of my brain assumed "make -k" would not just "keep going" but also ignore errors. That's not the case of course. I suppose we could disable -o pipefail for the test step. On the other hand, we should make these tests pass :-)...

...ders at imgtec.com> wrote: > >> Ben reports that he didn't get a tarball even after the rpath fix and > >> had to disable -o pipefail to get one. Still not sure what caused > >> this. > > > > 'make check' failures can cause this. I had to revert r241599 to get a > package. > > Oh, I'm silly. Some part of my brain assumed "make -k" would not just > "keep going" but also ignore errors. That's not the case of course. > > I suppose we could disable -o pipefail for the test step. On the other > hand, w...

Hi, I have tagged 3.6.2-final, so testers can start building and uploading -final binaries. There was only one change between 3.6.2-rc1 and 3.6.2-final, which was a patch to the R600 backend to fix the build with VS2012. Running a full regression suite is probably not necessary, but you still can if you want to be extra careful. -Tom

Hi, @CC'ing Hans because this will likely be of interest to you. Right I've started trying to build LLVM inside an Ubuntu chroot (Ubuntu 14.04LTS Docker image) and I've already come across a pretty bad bug in the ``test-release.sh`` script which potentially means that builds and/or tests could potentially fail without anyone noticing (unless someone carefully looks through the logs)

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release