I am happy to report our new Jenkins based build cluster is up and running: http://lab.llvm.org:8080/green/ <http://lab.llvm.org:8080/green/> This cluster is a major hardware update. The cluster has 10 builders + the Jenkins master. All builders have SSDs and enough RAM to do LTO builds of clang. Currently the cluster has: a cmake + ninja incremental builder a configure + make stage 1 builder a configure + make stage 2 builder with LTO a O3 LTO performance tracker In the near future other jobs will be added: LLDB O0 -g performance tracker libcxx tester configure + make stage 3 build When I am convinced things are working, I will enabled emails to developers, and the IRC bot. This cluster is a replacement for the old Darwin buildbots here: http://lab.llvm.org:8013/builders -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141027/46f64967/attachment.html>
On Mon, Oct 27, 2014 at 10:22 AM, Chris Matthews <chris.matthews at apple.com> wrote:> I am happy to report our new Jenkins based build cluster is up and running: > > http://lab.llvm.org:8080/green/ > > This cluster is a major hardware update. The cluster has 10 builders + the > Jenkins master. All builders have SSDs and enough RAM to do LTO builds of > clang. > > Currently the cluster has: > > - a cmake + ninja incremental builder > - a configure + make stage 1 builder > - a configure + make stage 2 builder with LTO > - a O3 LTO performance tracker > > > In the near future other jobs will be added: > > - LLDB > - O0 -g performance tracker > >Would this potentially include size tracking, too? (little harder to do if it's self-hosting, since the newer compiler would have more/different code, thus changing the size of debug info - so we might need some immutable code to do this analysis on (even just a predefined version of LLVM would be an option))> > - libcxx tester > - configure + make stage 3 build > > > When I am convinced things are working, I will enabled emails to > developers, and the IRC bot. > > This cluster is a replacement for the old Darwin buildbots here: > > http://lab.llvm.org:8013/builders > > > _______________________________________________ > 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/20141027/2c637e31/attachment.html>
On 27 October 2014 10:22, Chris Matthews <chris.matthews at apple.com> wrote:> I am happy to report our new Jenkins based build cluster is up and running:Nice!> This cluster is a major hardware update. The cluster has 10 builders + the > Jenkins master. All builders have SSDs and enough RAM to do LTO builds of > clang.Out of curiosity, what is that amount of RAM at the moment? Cheers. Tim.
> On Oct 27, 2014, at 10:30 AM, Tim Northover <t.p.northover at gmail.com> wrote: > > On 27 October 2014 10:22, Chris Matthews <chris.matthews at apple.com> wrote: >> I am happy to report our new Jenkins based build cluster is up and running: > > Nice! > >> This cluster is a major hardware update. The cluster has 10 builders + the >> Jenkins master. All builders have SSDs and enough RAM to do LTO builds of >> clang. > > Out of curiosity, what is that amount of RAM at the moment? >16GB. 16GB seems to not swap for a LTO build with -j 2.> Cheers. > > Tim.
So, I'm really unhappy with the proliferation of build masters. I used to have a single webpage to go to and see whether I broke builders. I don't even know how many I have now.... Is there a concrete plan to get back to a single build master? The Jenkins page you pointed me too seems completely OS X specific... =[ On Mon, Oct 27, 2014 at 10:22 AM, Chris Matthews <chris.matthews at apple.com> wrote:> I am happy to report our new Jenkins based build cluster is up and running: > > http://lab.llvm.org:8080/green/ > > This cluster is a major hardware update. The cluster has 10 builders + the > Jenkins master. All builders have SSDs and enough RAM to do LTO builds of > clang. > > Currently the cluster has: > > - a cmake + ninja incremental builder > - a configure + make stage 1 builder > - a configure + make stage 2 builder with LTO > - a O3 LTO performance tracker > > > In the near future other jobs will be added: > > - LLDB > - O0 -g performance tracker > - libcxx tester > - configure + make stage 3 build > > > When I am convinced things are working, I will enabled emails to > developers, and the IRC bot. > > This cluster is a replacement for the old Darwin buildbots here: > > http://lab.llvm.org:8013/builders > > > _______________________________________________ > 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/20141027/b08db0d2/attachment.html>
> On Oct 27, 2014, at 10:30 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Mon, Oct 27, 2014 at 10:22 AM, Chris Matthews <chris.matthews at apple.com <mailto:chris.matthews at apple.com>> wrote: > I am happy to report our new Jenkins based build cluster is up and running: > > http://lab.llvm.org:8080/green/ <http://lab.llvm.org:8080/green/> > > This cluster is a major hardware update. The cluster has 10 builders + the Jenkins master. All builders have SSDs and enough RAM to do LTO builds of clang. > > Currently the cluster has: > a cmake + ninja incremental builder > a configure + make stage 1 builder > a configure + make stage 2 builder with LTO > a O3 LTO performance tracker > > In the near future other jobs will be added: > LLDB > O0 -g performance tracker > > Would this potentially include size tracking, too? (little harder to do if it's self-hosting, since the newer compiler would have more/different code, thus changing the size of debug info - so we might need some immutable code to do this analysis on (even just a predefined version of LLVM would be an option))Out of the box, there is no size tracking on the NT performance suite. This is our standard performance test suite. We do have some code for reporting generated executable size in other parts of LNT though. Patches welcome to expand that to the NT test suite.> > libcxx tester > configure + make stage 3 build > > When I am convinced things are working, I will enabled emails to developers, and the IRC bot. > > This cluster is a replacement for the old Darwin buildbots here: > > http://lab.llvm.org:8013/builders <http://lab.llvm.org:8013/builders> > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu> http://llvm.cs.uiuc.edu <http://llvm.cs.uiuc.edu/> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev <http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141027/8d91c750/attachment.html>
Hi Chris, We're also using Jenkins for LLVM testing, but our setup is a lot more primitive than this! Do you plan on sharing the configuration scripts and set of plugins that you're using? David On 27 Oct 2014, at 17:22, Chris Matthews <chris.matthews at apple.com> wrote:> I am happy to report our new Jenkins based build cluster is up and running: > > http://lab.llvm.org:8080/green/ > > This cluster is a major hardware update. The cluster has 10 builders + the Jenkins master. All builders have SSDs and enough RAM to do LTO builds of clang. > > Currently the cluster has: > • a cmake + ninja incremental builder > • a configure + make stage 1 builder > • a configure + make stage 2 builder with LTO > • a O3 LTO performance tracker > > In the near future other jobs will be added: > • LLDB > • O0 -g performance tracker > • libcxx tester > • configure + make stage 3 build > > When I am convinced things are working, I will enabled emails to developers, and the IRC bot. > > This cluster is a replacement for the old Darwin buildbots here: > > http://lab.llvm.org:8013/builders > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> On Oct 27, 2014, at 10:39 AM, Chandler Carruth <chandlerc at google.com> wrote: > > So, I'm really unhappy with the proliferation of build masters. I used to have a single webpage to go to and see whether I broke builders. I don't even know how many I have now....While I agree that having a single page would be really nice; technically, the old buildbots that the new Jenkins system replaces (http://lab.llvm.org:8013/) never showed up on http://lab.llvm.org:8011/ either. -- adrian> > Is there a concrete plan to get back to a single build master? The Jenkins page you pointed me too seems completely OS X specific... =[ > > On Mon, Oct 27, 2014 at 10:22 AM, Chris Matthews <chris.matthews at apple.com> wrote: > I am happy to report our new Jenkins based build cluster is up and running: > > http://lab.llvm.org:8080/green/ > > This cluster is a major hardware update. The cluster has 10 builders + the Jenkins master. All builders have SSDs and enough RAM to do LTO builds of clang. > > Currently the cluster has: > • a cmake + ninja incremental builder > • a configure + make stage 1 builder > • a configure + make stage 2 builder with LTO > • a O3 LTO performance tracker > > In the near future other jobs will be added: > • LLDB > • O0 -g performance tracker > • libcxx tester > • configure + make stage 3 build > > When I am convinced things are working, I will enabled emails to developers, and the IRC bot. > > This cluster is a replacement for the old Darwin buildbots here: > > http://lab.llvm.org:8013/builders > > > _______________________________________________ > 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
I can see why that would annoy you. The intent here was to beef up the OS X testing, which had become really weak. This was a lateral move, we replaced an old build master that was OS X with a new build master which is OS X. At a technical level, there are lots of ways we could have a unified view over all of the CI systems. We need to sort out the who and what of project like that.> On Oct 27, 2014, at 10:39 AM, Chandler Carruth <chandlerc at google.com> wrote: > > So, I'm really unhappy with the proliferation of build masters. I used to have a single webpage to go to and see whether I broke builders. I don't even know how many I have now.... > > Is there a concrete plan to get back to a single build master? The Jenkins page you pointed me too seems completely OS X specific... =[ > > On Mon, Oct 27, 2014 at 10:22 AM, Chris Matthews <chris.matthews at apple.com <mailto:chris.matthews at apple.com>> wrote: > I am happy to report our new Jenkins based build cluster is up and running: > > http://lab.llvm.org:8080/green/ <http://lab.llvm.org:8080/green/> > > This cluster is a major hardware update. The cluster has 10 builders + the Jenkins master. All builders have SSDs and enough RAM to do LTO builds of clang. > > Currently the cluster has: > a cmake + ninja incremental builder > a configure + make stage 1 builder > a configure + make stage 2 builder with LTO > a O3 LTO performance tracker > > In the near future other jobs will be added: > LLDB > O0 -g performance tracker > libcxx tester > configure + make stage 3 build > > When I am convinced things are working, I will enabled emails to developers, and the IRC bot. > > This cluster is a replacement for the old Darwin buildbots here: > > http://lab.llvm.org:8013/builders <http://lab.llvm.org:8013/builders> > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu> http://llvm.cs.uiuc.edu <http://llvm.cs.uiuc.edu/> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev <http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141027/fd8cb93c/attachment.html>
Yes! I should have mentioned this in the email. The code will go into zorg soon.> On Oct 27, 2014, at 10:47 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > Hi Chris, > > We're also using Jenkins for LLVM testing, but our setup is a lot more primitive than this! Do you plan on sharing the configuration scripts and set of plugins that you're using? > > David > > On 27 Oct 2014, at 17:22, Chris Matthews <chris.matthews at apple.com> wrote: > >> I am happy to report our new Jenkins based build cluster is up and running: >> >> http://lab.llvm.org:8080/green/ >> >> This cluster is a major hardware update. The cluster has 10 builders + the Jenkins master. All builders have SSDs and enough RAM to do LTO builds of clang. >> >> Currently the cluster has: >> • a cmake + ninja incremental builder >> • a configure + make stage 1 builder >> • a configure + make stage 2 builder with LTO >> • a O3 LTO performance tracker >> >> In the near future other jobs will be added: >> • LLDB >> • O0 -g performance tracker >> • libcxx tester >> • configure + make stage 3 build >> >> When I am convinced things are working, I will enabled emails to developers, and the IRC bot. >> >> This cluster is a replacement for the old Darwin buildbots here: >> >> http://lab.llvm.org:8013/builders >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Chris, What are the limitations of zorg/BuildBot that caused you to go with Jenkins instead? Jon On 10/27/14 10:39 AM, Chandler Carruth wrote:> So, I'm really unhappy with the proliferation of build masters. I used to > have a single webpage to go to and see whether I broke builders. I don't > even know how many I have now.... > > Is there a concrete plan to get back to a single build master? The Jenkins > page you pointed me too seems completely OS X specific... =[ > > On Mon, Oct 27, 2014 at 10:22 AM, Chris Matthews <chris.matthews at apple.com> > wrote: > >> I am happy to report our new Jenkins based build cluster is up and running: >> >> http://lab.llvm.org:8080/green/ >> >> This cluster is a major hardware update. The cluster has 10 builders + the >> Jenkins master. All builders have SSDs and enough RAM to do LTO builds of >> clang. >> >> Currently the cluster has: >> >> - a cmake + ninja incremental builder >> - a configure + make stage 1 builder >> - a configure + make stage 2 builder with LTO >> - a O3 LTO performance tracker >> >> >> In the near future other jobs will be added: >> >> - LLDB >> - O0 -g performance tracker >> - libcxx tester >> - configure + make stage 3 build >> >> >> When I am convinced things are working, I will enabled emails to >> developers, and the IRC bot. >> >> This cluster is a replacement for the old Darwin buildbots here: >> >> http://lab.llvm.org:8013/builders >> >> >> _______________________________________________ >> 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 >-- Jon Roelofs jonathan at codesourcery.com CodeSourcery / Mentor Embedded
Joerg Sonnenberger
2014-Oct-27 19:03 UTC
[LLVMdev] New OS X and Jenkins based build cluster
On Mon, Oct 27, 2014 at 10:22:56AM -0700, Chris Matthews wrote:> Currently the cluster has: > a cmake + ninja incremental builderWould it be possible to archive installations and provide (registered) developers access for fast bisection? Personally, I tend to need bisections at least a hand full of times per month. With the hardware I have at hand, that normally needs 3h+. Being able to do an initial pass to cut it down e.g. to 32 revisions would greatly reduce the amount of time as there is hopefully only one major API change in such a time frame. Joerg
Yes, this is a great idea, and something I have already looked at a little bit. Two things we need: a good local bisection client, and some place to store the artifacts that is high bandwidth and available (I don’t think it is a good idea to host them from the lab itself). The compilers are 60mb-90mb each.> On Oct 27, 2014, at 12:03 PM, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > > On Mon, Oct 27, 2014 at 10:22:56AM -0700, Chris Matthews wrote: >> Currently the cluster has: >> a cmake + ninja incremental builder > > Would it be possible to archive installations and provide (registered) > developers access for fast bisection? Personally, I tend to need > bisections at least a hand full of times per month. With the hardware I > have at hand, that normally needs 3h+. Being able to do an initial pass > to cut it down e.g. to 32 revisions would greatly reduce the amount of > time as there is hopefully only one major API change in such a time > frame. > > Joerg > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Maybe Matching Threads
- [LLVMdev] New OS X and Jenkins based build cluster
- [LLVMdev] Plans for the Apple supported Darwin buildbot cluster
- [LLVMdev] llvmlab (phased buildmaster) is in production mode!
- Zorg migration to GitHub/monorepo
- Buildbot numbers for the week of 9/25/2016 - 10/1/2016