Hey Galina, Will; I've been working to revive the PPC64 build bots, and succeeded, but not for the right reasons. There were still bootstrap assertion failures and other pretty blatant errors. Then we figured out why: the Clang bootstrapping build bots for Power7 are not actually running any of the Clang tests! Could one of you tweak this build bot's configuration to match the other bootstrap bot configurations that run both LLVM and Clang tests? Is there a a Clang PPC64 build bot that *doesn't* self-host so we can get faster turn around? I think the ideal configuration is: 1) normal clang-test-only build bot 2) normal llvm-test-only build bot 3) bootstrap a new toolchain, and then run clang+llvm tests. Thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121209/5bdcf961/attachment.html>
On 09.12.2012, at 11:19, Chandler Carruth <chandlerc at gmail.com> wrote:> Hey Galina, Will; > > I've been working to revive the PPC64 build bots, and succeeded, but not for the right reasons. There were still bootstrap assertion failures and other pretty blatant errors. Then we figured out why: the Clang bootstrapping build bots for Power7 are not actually running any of the Clang tests! > > Could one of you tweak this build bot's configuration to match the other bootstrap bot configurations that run both LLVM and Clang tests?This turns out to be a bug in our testing infrastructure (http://llvm.org/bugs/show_bug.cgi?id=13598). I added a workaround in r169695 and it seems that the bots are running tests now. The python that ships with fedora 17 seems to use a lot of address space for thread-local storage and exceeded the limit set by the makefile. Another problem was that the bot reports a green status even though lit aborted. Could be a problem in the buildbot software somewhere. I attached a log from one of the last build runs so this doesn't get lost. -------------- next part -------------- A non-text attachment was scrubbed... Name: test.log Type: application/octet-stream Size: 2583 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121209/a7d7b732/attachment.obj> -------------- next part -------------- - Ben> > Is there a a Clang PPC64 build bot that *doesn't* self-host so we can get faster turn around? > > I think the ideal configuration is: > > 1) normal clang-test-only build bot > 2) normal llvm-test-only build bot > 3) bootstrap a new toolchain, and then run clang+llvm tests. > > Thoughts? > _______________________________________________ > cfe-dev mailing list > cfe-dev at cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Chandler Carruth <chandlerc at gmail.com> wrote:> I've been working to revive the PPC64 build bots, and succeeded, but > not for the right reasons. There were still bootstrap assertion > failures and other pretty blatant errors. Then we figured out why: > the Clang bootstrapping build bots for Power7 are not actually > running any of the Clang tests! > > Could one of you tweak this build bot's configuration to match the > other bootstrap bot configurations that run both LLVM and Clang tests?Maybe I'm confused somehow, but I thought this one: http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2 does bootstrap and then run both LLVM and Clang tests (successfully): http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/775/steps/check-all_1/logs/stdio The other Clang PPC64 build bot tries to run lnt.nightly-test: http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux but fails (and has always been failing); one problem seems to be that altivec is disabled for some reason? It's been on my to-do list to check what's going on here ...> Is there a a Clang PPC64 build bot that *doesn't* self-host so we > can get faster turn around? > > I think the ideal configuration is: > > 1) normal clang-test-only build bot > 2) normal llvm-test-only build bot > 3) bootstrap a new toolchain, and then run clang+llvm tests.Besides the two bots mentioned above, there's also two LLVM bots: http://lab.llvm.org:8011/builders/llvm-ppc64-linux1 http://lab.llvm.org:8011/builders/llvm-ppc64-linux2 which simply build and test LLVM only. (Not sure why there's two of them, they seem to be doing the same thing. Will?) Bye, Ulrich
On Mon, 2012-12-10 at 15:19 +0100, Ulrich Weigand wrote:> Chandler Carruth <chandlerc at gmail.com> wrote: > > > I've been working to revive the PPC64 build bots, and succeeded, but > > not for the right reasons. There were still bootstrap assertion > > failures and other pretty blatant errors. Then we figured out why: > > the Clang bootstrapping build bots for Power7 are not actually > > running any of the Clang tests! > > > > Could one of you tweak this build bot's configuration to match the > > other bootstrap bot configurations that run both LLVM and Clang tests?Hi, So ignoring the ppc64-elf-linux2 bot (which is redundant wrt the ppc64-elf-linux1 bot), Powerpc64 has three unique buildbots going; the relevant 'factory' entries for them are so: LLVMBuilder.getLLVMBuildFactory("ppc64-linux-gnu", LNTBuilder.getLNTFactory(triple='ppc64-elf-linux1', ClangBuilder.getClangBuildFactory(triple='ppc64-elf-linux', I'm happy to change those or add another if desired, but will need additional input on 'what'.> > Maybe I'm confused somehow, but I thought this one: > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2 > does bootstrap and then run both LLVM and Clang tests (successfully): > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/775/steps/check-all_1/logs/stdioCorrect, or at least that is the intent.> The other Clang PPC64 build bot tries to run lnt.nightly-test: > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux > but fails (and has always been failing); one problem seems to > be that altivec is disabled for some reason? It's been on my > to-do list to check what's going on here ...Correct. This was the first clang buildbot that I set up, and it is configured to do the LNT tests.> > Is there a a Clang PPC64 build bot that *doesn't* self-host so we > > can get faster turn around? > > > > I think the ideal configuration is: > > > > 1) normal clang-test-only build bot > > 2) normal llvm-test-only build bot > > 3) bootstrap a new toolchain, and then run clang+llvm tests. > > Besides the two bots mentioned above, there's also two LLVM bots: > http://lab.llvm.org:8011/builders/llvm-ppc64-linux1 > http://lab.llvm.org:8011/builders/llvm-ppc64-linux2 > which simply build and test LLVM only. (Not sure why there's > two of them, they seem to be doing the same thing. Will?)They are on different host systems, but are redundant with respect to each other as far as the llvm testing goes. If having two complicates things, I can disable the second. Thanks, -Will> Bye, > Ulrich >
On 10.12.2012, at 15:19, Ulrich Weigand <Ulrich.Weigand at de.ibm.com> wrote:> Chandler Carruth <chandlerc at gmail.com> wrote: > >> I've been working to revive the PPC64 build bots, and succeeded, but >> not for the right reasons. There were still bootstrap assertion >> failures and other pretty blatant errors. Then we figured out why: >> the Clang bootstrapping build bots for Power7 are not actually >> running any of the Clang tests! >> >> Could one of you tweak this build bot's configuration to match the >> other bootstrap bot configurations that run both LLVM and Clang tests? > > Maybe I'm confused somehow, but I thought this one: > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2 > does bootstrap and then run both LLVM and Clang tests (successfully): > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/775/steps/check-all_1/logs/stdioIt does now, but failed to do so until r169695 due to a incompatibility of LLVM's makefiles and Fedora 17's version of python. It still reported a (false) green status, which is indeed confusing and probably a different bug in our buildbot infrastructure. The LLVM bots were unaffected, they're still running on Fedora 16. Now the bot successfully runs all clang regression tests, which is great and very helpful by reporting new regressions early. - Ben> > The other Clang PPC64 build bot tries to run lnt.nightly-test: > http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux > but fails (and has always been failing); one problem seems to > be that altivec is disabled for some reason? It's been on my > to-do list to check what's going on here ... > >> Is there a a Clang PPC64 build bot that *doesn't* self-host so we >> can get faster turn around? >> >> I think the ideal configuration is: >> >> 1) normal clang-test-only build bot >> 2) normal llvm-test-only build bot >> 3) bootstrap a new toolchain, and then run clang+llvm tests. > > Besides the two bots mentioned above, there's also two LLVM bots: > http://lab.llvm.org:8011/builders/llvm-ppc64-linux1 > http://lab.llvm.org:8011/builders/llvm-ppc64-linux2 > which simply build and test LLVM only. (Not sure why there's > two of them, they seem to be doing the same thing. Will?) > > Bye, > Ulrich > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev