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
Yes. On Mon, Nov 10, 2008 at 4:45 PM, David Greene <dag at cray.com> wrote:> 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 > _______________________________________________ > 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 16:50, Daniel Berlin wrote:> Yes.Cool. I'd like to look at installing something here. You offered to walk us through how to do this. I'll see if I can install buildbot here and then mail you back when I'm ready to go. -Dave> On Mon, Nov 10, 2008 at 4:45 PM, David Greene <dag at cray.com> wrote: > > 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 > > > > _______________________________________________ > > 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