All, We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in setting up your nightly tester. Thanks! -Tanya
Hello, On Jun 3, 2008, at 08:52 , Tanya Lattner wrote:> All, > > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform.I think I might be able to set up a nightly tester for Linux x86 (32- bit). Although I've been following LLVM for quite a while now, I feel like I can't really contribute to it, because of lack of time and knowledge. Hopefully this way I can contribute... I have some questions though: *) Is something more expected besides donating cycles-to-burn, e.g. active bug reporting/resolving of bugs found by the nightly tester and such? It's not that I'm not willing to (in fact, I'd love to), but I just wouldn't be able to find the time to do it properly. I try to report bugs I run into from time to time, but that's highly dependent on how busy I am doing my actual Phd work (to which LLVM is only partially related). *) I'll probably need the machine for experiments now and then, I'm guessing it's ok the nightly test isn't run every single night? greetings, Kenneth> > > Directions to set up a tester are here: > http://llvm.org/docs/TestingGuide.html#nightly > > These directions could be improved of course. If you have any > questions, I will be happy to assist you in setting up your nightly > tester. > > Thanks! > -Tanya > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-- Computer Science is no more about computers than astronomy is about telescopes. (E. W. Dijkstra) Kenneth Hoste ELIS - Ghent University email: kenneth.hoste at elis.ugent.be blog: http://www.elis.ugent.be/~kehoste/blog website: http://www.elis.ugent.be/~kehoste
Am Montag, den 02.06.2008, 23:52 -0700 schrieb Tanya Lattner:> All, > > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. > > Directions to set up a tester are here: > http://llvm.org/docs/TestingGuide.html#nightly > > These directions could be improved of course. If you have any > questions, I will be happy to assist you in setting up your nightly > tester.I had planned to try again once 2.3 is out, but if you're short on Linux testers, I'll join in. Available platforms: * x86_64 * i686 compatibility Given that I had problems getting the latter to run, I think I should concentrate on x86_64. Should I switch PIC off for that? Regards, Jo
On Tue, Jun 3, 2008 at 1:03 AM, Kenneth Hoste <kenneth.hoste at ugent.be> wrote:> Although I've been following LLVM for quite a while now, I feel like I > can't really contribute to it, because of lack of time and knowledge. > Hopefully this way I can contribute... >Excellent! I have some questions though:> > *) Is something more expected besides donating cycles-to-burn, e.g. > active bug reporting/resolving of bugs found by the nightly tester and > such? > It's not that I'm not willing to (in fact, I'd love to), but I just > wouldn't be able to find the time to do it properly. I try to report > bugs I run into from time to time, but that's highly dependent on how > busy I am doing my actual Phd work (to which LLVM is only partially > related).Not necessary at all, while always appreciated. I think the biggest thing would be that *if* you notice something that wouldn't even show up in the nightly (like a complete failure to build or something) to maybe send an email, especially if its repeatable, and continues. For the most part however, there are lots of people willing and eager to fix bugs once they know about them. Additionally the nightly testers provide other insight regarding performance and different system behaviors.> *) I'll probably need the machine for experiments now and then, I'm > guessing it's ok the nightly test isn't run every single night? >The nightly tester system is well equipped for handling even moderately intermittent submissions -- I think you'll be fine! =] -Chandler> > greetings, > > Kenneth > > > > > > > Directions to set up a tester are here: > > http://llvm.org/docs/TestingGuide.html#nightly > > > > These directions could be improved of course. If you have any > > questions, I will be happy to assist you in setting up your nightly > > tester. > > > > Thanks! > > -Tanya > > > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > -- > > Computer Science is no more about computers than astronomy is about > telescopes. (E. W. Dijkstra) > > Kenneth Hoste > ELIS - Ghent University > email: kenneth.hoste at elis.ugent.be > blog: http://www.elis.ugent.be/~kehoste/blog<http://www.elis.ugent.be/%7Ekehoste/blog> > website: http://www.elis.ugent.be/~kehoste<http://www.elis.ugent.be/%7Ekehoste> > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080603/28230541/attachment.html>
Hi Tanya, I got the go-ahead from Laurent Guerby for using the gcc compile farm for running the llvm nightly tester (http://gcc.gnu.org/wiki/CompileFarm). I will try to set this up, but in fact anyone can apply for a login as described at the above webpage. Ciao, Duncan. PS: The machines are all running linux and are mostly amd64 or x86-32, but there is also an alpha.
Wow, this is great news!! Thanks Duncan! -Tanya On Tue, 3 Jun 2008, Duncan Sands wrote:> Hi Tanya, I got the go-ahead from Laurent Guerby > for using the gcc compile farm for running the llvm > nightly tester (http://gcc.gnu.org/wiki/CompileFarm). > I will try to set this up, but in fact anyone can > apply for a login as described at the above webpage. > > Ciao, > > Duncan. > > PS: The machines are all running linux and are mostly > amd64 or x86-32, but there is also an alpha. >
>> We are in desperate need of linux x86 testers (32 or 64 bit). If you >> could set one up, the LLVM project would be very grateful. Right now >> we have virtually no testers covering this platform. > > I think I might be able to set up a nightly tester for Linux x86 (32- > bit). > > Although I've been following LLVM for quite a while now, I feel like I > can't really contribute to it, because of lack of time and knowledge. > Hopefully this way I can contribute...That would be great! Thank you!> I have some questions though: > > *) Is something more expected besides donating cycles-to-burn, e.g. > active bug reporting/resolving of bugs found by the nightly tester and > such?The best case scenario is when someone actually watches the nightly tester, but at this point, we will take anything (even if its just cycles). It would be helpful if you do see a failure, to either bring it to attention on the llvm-testresults mailing list or to file a PR. People are supposed to watch the nightly testers when they commit, but as you can imagine.. that doesn't always happen. However, if you don't have time to do this.. then don't worry.> It's not that I'm not willing to (in fact, I'd love to), but I just > wouldn't be able to find the time to do it properly. I try to report > bugs I run into from time to time, but that's highly dependent on how > busy I am doing my actual Phd work (to which LLVM is only partially > related).Yes, I understand.> *) I'll probably need the machine for experiments now and then, I'm > guessing it's ok the nightly test isn't run every single night?You can run it as often as you like. The only downside is that it makes it harder to track down problems, but since we don't have any linux testers at the moment.. occasional testing is better than none at all :) -Tanya> greetings, > > Kenneth > >> >> >> Directions to set up a tester are here: >> http://llvm.org/docs/TestingGuide.html#nightly >> >> These directions could be improved of course. If you have any >> questions, I will be happy to assist you in setting up your nightly >> tester. >> >> Thanks! >> -Tanya >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >
> I had planned to try again once 2.3 is out, but if you're short on Linux > testers, I'll join in. > > Available platforms: > * x86_64 > * i686 compatibility > Given that I had problems getting the latter to run, I think I should > concentrate on x86_64. > Should I switch PIC off for that?Thanks! Running a linux tester would be a huge help for the project. However, I am not sure why you need to switch PIC off. Could you explain a bit more? -Tanya
Hello list! Tanya Lattner wrote:> We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform.I've run the test last night to see how long it takes, and I can afford to cronjob it for the night. I didn't quite realize it would automatically send the report, but it did [1] and there are a few test failure from the Frontend{C,C++} directories. I suppose this is because I have llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is there a specific version of llvm-gcc that is prefered for nightly tests? Shall I go with the latest stable one? 4.0 or 4.2? What does -enable-linscan do? It's not referenced anywhere in NewNightlyTest.pl, but it's given as example in [2]. I will also take the freedom to disable the nightly test if I need the CPU cycles for something else during a night. jlh [1] http://llvm.org/nightlytest/test.php?machine=288&night=6315 [2] http://llvm.org/docs/TestingGuide.html#nightly
On Jun 5, 2008, at 5:16 AM, jlh wrote:> I suppose this is because I have > llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is > there a specific version of llvm-gcc that is prefered for nightly > tests? Shall I go with the latest stable one? 4.0 or 4.2?4.2
> I've run the test last night to see how long it takes, and I can > afford to cronjob it for the night.Great!> I didn't quite realize it would automatically send the report, but > it did [1] and there are a few test failure from the > Frontend{C,C++} directories. I suppose this is because I have > llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is > there a specific version of llvm-gcc that is prefered for nightly > tests? Shall I go with the latest stable one? 4.0 or 4.2?llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind that you need to keep llvm-gcc in sync with llvm (same revision number).> What does -enable-linscan do? It's not referenced anywhere in > NewNightlyTest.pl, but it's given as example in [2].Its an option to enable linear scan register allocator. It probably wasn't default when the docs were written.> I will also take the freedom to disable the nightly test if I need > the CPU cycles for something else during a night.Understood. -Tanya> > jlh > > [1] http://llvm.org/nightlytest/test.php?machine=288&night=6315 > [2] http://llvm.org/docs/TestingGuide.html#nightly > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >