No :) I'm trying to start by having something that keeps people from breaking the build and tests (by letting them submit patches and being whiny 3 minutes after something breaks). Once that is done, we can move to something that keeps all the languages in good shape. I think if i simply made it do everything at once, people would just ignore it. At least, that's my experience :) I'm happy to have people edit the config files the master uses to tell the slaves what to do in terms of building/etc On Mon, Nov 3, 2008 at 3:49 PM, Bill Wendling <isanbard at gmail.com> wrote:> Daniel, > > Thanks! Is this doing a build of Ada and Fortran? :-) > > -bw > > On Sun, Nov 2, 2008 at 1:02 PM, Daniel Berlin <dberlin at dberlin.org> wrote: >> I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall >> It builds every single revision of llvm, runs the testsuite, and >> reports the results. It takes about 3 minutes per build+test right >> now (it's an 8 core machine). >> >> Currently i have it building x86_64-linux. >> Setting up a builder/slave for any platform would be trivial. >> I simply don't have machines running anything but x86_64-linux that i >> can use for this purpose. >> >> It simply requires installing buildbot , and pointing it at this >> buildbot as it's master. >> You only need to be able to connect to the outside world, you don't >> have to be able to receive connections. >> Let me know if you have a machine/platform you want to connect to this >> as a build slave and i can walk you through it. >> >> It can also test patches for you and give you the results (currently >> this requires buildbot be installed on your machine, i will make it >> web/email accessible) >> >> I will add the dejagnu logs to the clickable links, as well as make it >> link to just the list of FAIL's so you don't have to search the log. >> >> I will also make it bootstrap llvm-gcc once or twice a day. >> --Dan >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
That's cool. And I agree that it if didn't work, people would ignore it. :-) At the moment, we have only Duncan and a couple of Fortran guys to tell us when an Apple merge has broken something. I'm sure that they would welcome an early detection system. :-) -bw On Mon, Nov 3, 2008 at 1:40 PM, Daniel Berlin <dberlin at dberlin.org> wrote:> No :) > > I'm trying to start by having something that keeps people from > breaking the build and tests (by letting them submit patches and being > whiny 3 minutes after something breaks). > Once that is done, we can move to something that keeps all the > languages in good shape. > > I think if i simply made it do everything at once, people would just > ignore it. At least, that's my experience :) > > I'm happy to have people edit the config files the master uses to tell > the slaves what to do in terms of building/etc > > On Mon, Nov 3, 2008 at 3:49 PM, Bill Wendling <isanbard at gmail.com> wrote: >> Daniel, >> >> Thanks! Is this doing a build of Ada and Fortran? :-) >> >> -bw >> >> On Sun, Nov 2, 2008 at 1:02 PM, Daniel Berlin <dberlin at dberlin.org> wrote: >>> I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall >>> It builds every single revision of llvm, runs the testsuite, and >>> reports the results. It takes about 3 minutes per build+test right >>> now (it's an 8 core machine). >>> >>> Currently i have it building x86_64-linux. >>> Setting up a builder/slave for any platform would be trivial. >>> I simply don't have machines running anything but x86_64-linux that i >>> can use for this purpose. >>> >>> It simply requires installing buildbot , and pointing it at this >>> buildbot as it's master. >>> You only need to be able to connect to the outside world, you don't >>> have to be able to receive connections. >>> Let me know if you have a machine/platform you want to connect to this >>> as a build slave and i can walk you through it. >>> >>> It can also test patches for you and give you the results (currently >>> this requires buildbot be installed on your machine, i will make it >>> web/email accessible) >>> >>> I will add the dejagnu logs to the clickable links, as well as make it >>> link to just the list of FAIL's so you don't have to search the log. >>> >>> I will also make it bootstrap llvm-gcc once or twice a day. >>> --Dan >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
> That's cool. And I agree that it if didn't work, people would ignore > it. :-) At the moment, we have only Duncan and a couple of Fortran > guys to tell us when an Apple merge has broken something. I'm sure > that they would welcome an early detection system. :-)My tester builds Ada and Fortran llvm-gcc nightly on x86-32, and Fortran nightly on x86-64 (Ada doesn't build on x86-64 due to a regalloc bug, PR2556 :( ). At some point it would be nice to have the buildbot build Fortran since (1) this is easy to do (no special requirements), and (2) hopefully Fortran will be part of the next release. Ciao, Duncan.