|
From: Florian K. <br...@ac...> - 2011-11-07 22:33:41
|
On 11/07/2011 04:17 PM, Philippe Waroquiers wrote: > gcc compile farm has received a bbbbbigggggg power7 computer (64 processors, 64Gb memory) from IBM, > installed with fedora16. > > Unless someone is already busy setting up a nightly test on a power7, > I can setup a nightly ppc64/fedora16 test on this computer. > Yes, please do. One thing. If you're looking at nightly/README.txt make sure step #1 in the "SETTING UP" section happens every night. That way, when somebody changes the nightly script, we see the changes in the next build. My crontab script looks like so: #!/bin/sh cd /opt rm -rf ./nightly svn co svn://svn.valgrind.org/valgrind/trunk/nightly nightly ./nightly/bin/nightly /opt/nightly z900 exit 0 That README file should be improved in that respect.... Ah well, one of these days... > Note: I just have one problem : I did one build + regtest on this computer, and had drd running on > annotate_hbefore that took about one hour of cpu (then I killed it). > gcc compile farm highly recommends to avoid such looping tests (so, I will put a ulimit > in cpu when launching the nightly test). > Perhaps better disable the testcase, so we make it all the way through the suite. Florian |