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
This is great stuff. Thanks Daniel. Evan On Nov 2, 2008, at 1:02 PM, Daniel Berlin 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
Hi Daniel,> 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).how does it report the results? Can it email the mailing list if the build fails for example? Ciao, Duncan.
On Mon, Nov 3, 2008 at 2:43 AM, Duncan Sands <duncan.sands at math.u-psud.fr> wrote:> Hi Daniel, > >> 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). > > how does it report the results? Can it email the mailing list if the > build fails for example? >It can, it could also email the list only if it goes from success to failure (so that continual failures don't generate an email each), etc. I haven't set up the email notifier yet, i am still getting it to add the test result links nicely first, then i'll get the email notifier added. (It's a matter of a few lines of config :P)> Ciao, > > Duncan. >
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 >
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 >
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'd like to volunteer a Windows build slave, building via Visual Studio (or CMake->VS) as that's the configuration I care about. Is that plausible? Before worrying about the buildbot part, I suppose I need to be able run the tests. Do people do that regularly on Windows? It seems the makefiles depend on running configure, but perhaps some (scary) hybrid of building via VS, and running 'make check' under devilspawn^Hcygwin is possible? scott
On Mon, Nov 3, 2008 at 4:58 PM, Scott Graham <scott.llvm at h4ck3r.net> wrote:> 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'd like to volunteer a Windows build slave, building via Visual > Studio (or CMake->VS) as that's the configuration I care about. Is > that plausible?If you can build it via a series of repeatable steps, it should be doable. You can have different build steps for different builders/platforms if you want, so for win32 we could do whatever is necessary to make it run there.> > Before worrying about the buildbot part, I suppose I need to be able > run the tests. Do people do that regularly on Windows? It seems the > makefiles depend on running configure, but perhaps some (scary) hybrid > of building via VS, and running 'make check' under devilspawn^Hcygwin > is possible? > > scott > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Hi Daniel, I see that you're doing a Debug build. Could you do a "Release" or "Release-Asserts" build instead? This will catch errors which developers won't normally see. -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 >
On Monday 10 November 2008 15:28, Bill Wendling wrote:> Hi Daniel, > > I see that you're doing a Debug build. Could you do a "Release" or > "Release-Asserts" build instead? This will catch errors which > developers won't normally see.I never knew about buildbot until just now. This could really help with the validation proposal I just posted. Can buildbot aggregate results from builds on various machines (.e.g each machine building and testing a different codegen target) and send reports through e-mail? -Dave> 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
Reasonably Related Threads
- [LLVMdev] Buildbot now up and new build failures
- [LLVMdev] Buildbot now up and new build failures
- [LLVMdev] Buildbot now up and new build failures
- [LLVMdev] FW: buildbot failure in llvm on llvm-i686-linux
- [LLVMdev] FW: buildbot failure in llvm on llvm-i686-linux