similar to: [LLVMdev] Plans for the Apple supported Darwin buildbot cluster

I'd be interested in seeing what you have planned upstreamed. I've used Jenkins on several projects. Will Zorg be a vehicle for transition, where buildbot slaves become Jenkins nodes defined in the project files? Do you see a majority of this this as a jenkins matrix project, or some other organization? Rick On 08/13/2014 05:09 AM, David Chisnall wrote: > On 12 Aug 2014, at

Yes! That would be really great! > On Aug 13, 2014, at 3:09 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > >> On 12 Aug 2014, at 19:34, Chris Matthews <chris.matthews at apple.com> wrote: >> >> The most notable change will be a switch from Buildbot to Jenkins. > > We're currently running LLVM test builds in Jenkins and I have patched

David, I like your patch. I applied the feedback in Phabricator and tested internally. Is it your intent to contribute the patch? I could commit the revised version on your behalf? > On Aug 14, 2014, at 2:41 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > I've put the diff in Phabricator here: > > http://reviews.llvm.org/D4901 > > If you think

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

On 14 August 2014 11:26, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > So you don't want to send it to the standard output. The things that want to parse it expect a file in the filesystem. So if you want the verbose build to be sticking it in a well-known file then I don't have strong objections, but it seems to be conflating two things. We run lit in -q mode in

On 14 August 2014 11:13, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > Our Jenkins config just runs llvm-lit manually after building (we use Ninja not make in Jenkins because it's vastly faster for incremental builds and we have several LLVM forks / versions that we test). I agree that having a make / ninja target for the check would be useful, but the lit option was the

> On Oct 7, 2015, at 3:28 PM, Renato Golin <renato.golin at linaro.org> wrote: > > On 7 October 2015 at 23:20, Chris Matthews <chris.matthews at apple.com> wrote: >> For instance, a build that fails with a ninja error, will say so, same with a >> svn failure or a Jenkins exception. > > Will these get mailed to developers? Or admins? Unfortunately, Jenkins

It looks like all sanitizer builder are still offline http://lab.llvm.org:8011/#/builders On Tue, 6 Oct 2020 at 00:34, Galina Kistanova via cfe-commits < cfe-commits at lists.llvm.org> wrote: > Hello everyone, > > The staging buildbot was up and running for 6 days now, and looks good. > > Tomorrow at 12:00 PM PDT we will switch the production buildbot to the new >

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

Our Flang-aarch64 buildbots just won't connect to the main Buildbot master anymore. I switched them to the staging buildbot master instead and it seems fine for now. Is there anything that we can/should tweak at our end? http://lab.llvm.org:8014/#/waterfall?tags=flang -Andrzej On 08/10/2020 00:31, Galina Kistanova via cfe-dev wrote: > They are online now -

Hi All, Recent conversations [1][2] would suggest we need to rethink zorg or at the very least improve the documentation. I've CC'ed Daniel Dunbar, Galina Kistanova and Duncan Sands because it seemed that they have contributed the most code to Zorg Organisation ========= The current organisation of the Zorg repository doesn't make a huge amount of sense from my perspective. There

Hello everyone, The buildbot upgrade is entering the phase when the results to become visible. No change is required at this time on any of the builders. The bot owners could upgrade the buildbot on build computers later, at their convenience, as this is not on the critical path. We are going to upgrade the staging bot first. Then, once that is stable and all detected issues are resolved, we

Hi Paula, This error is fine. The buildbot has tested the worker version. 0.8.x apparently does not have that method. The error gets handled gracefully on the server side. At least it seems so so far. That should not prevent your bot from connecting. Thanks Galina On Thu, Oct 8, 2020 at 2:11 PM Paula Askar <paulatoth at google.com> wrote: > Hey Andrzej, > > What are you seeing

On 14 August 2014 10:41, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > I've put the diff in Phabricator here: > > http://reviews.llvm.org/D4901 > > If you think it looks vaguely sensible then let me know and I'll commit it. Hi David, Is there an option for "make check-all"? Or do you have to call lit in a special way inside Jenkins? --renato

I was hoping to avoid the trouble of having to setup a master buildbot. But may be it's just easier to run Zorg as-is locally alongside the buildslave. I'll give that a go. Cheers, / Asiri On Fri, May 27, 2016 at 8:45 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > You don't really need to use the llvm builders infrastructure, just setup > a local jenkins (or

I just changed this build on green dragon to warn and email if warnings are found in the console log: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_build/ > On Mar 22, 2016, at 6:24 PM, David Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

Hi folks, *tl;dr* I'm having some trouble setting up a Windows buildbot and I'm looking for someone with LLVM-on-Windows experience to help me. *Long story* Hans Wennborg recently pointed <http://lists.llvm.org/pipermail/llvm-dev/2020-May/141803.html>out <http://lists.llvm.org/pipermail/llvm-dev/2020-May/141803.html>, that we're missing a 32 bit Windows buildbot and I

My thought was that its reasonable to expect no warnings when building from bootstrap (as you say) and the last release of Clang. Generally, I think we should work around warnings in the last release of Clang if only for the convenience of folks using that release to build stage1 and using Werror. Certainly, we tend to fix warnings even from earlier Clang versions and from GCC in order to keep

Hi, I had cloned zorg from https://llvm.org/svn/llvm-project/zorg/trunk, then I try to start the buildbot master located in buildbot/osuosl/master (the absolute path is /nfs/home/hongbin.zheng/buildbot/zorg/buildbot/osuosl/master) by simply typing "buildbot start" And I get something like this from my twistd.log: --- <exception caught here> --- File

On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think having -Werror bots is a good idea, at least when self hosting. > Non-self-hosting -Werror (i.e. with older versions of Clang, or with GCC, > etc.) might also be useful, but I'm less sure (since we can't fix those > warnings if the warning is the problem). On Tue, Mar