On 18 August 2016 at 15:21, Renato Golin <renato.golin at linaro.org> wrote:> On 18 August 2016 at 14:32, Alex Bradbury <asb at asbradbury.org> wrote: >> Good question, I didn't mention buildbots in this RFC as from a quick >> look at http://lab.llvm.org:8011/builders it didn't look like >> early-stage architecture ports tend to have one, and as you say >> check-all should be be enough initially. > > They normally don't. But your target won't be tested by any other > buildbot unless it's built by default, which only happens when it's > made official. > > So, either you have some local validation (buildbot, weekly build + > check-all, doesn't matter), with your target built in, or you won't > know when your tests regress.Obviously `./bin/llvm-lit -s -i ../test` is one of my most frequently executed commands, but we definitely want automation to pick up issues caused by changes elsewhere.>> I'm sure that we (i.e. >> lowRISC CIC) can support an additional buildbot when appropriate. Is >> there any recommendation on minimum specification? > > If you have a server which can do some LLVM builds (can be any arch), > then you just create a buildslave and add > -DLLVM_TARGETS_TO_BUILD=RISCV to the CMake options, running check-all. > > This doesn't need to be public, but you don't want to find test > failures only when we move your target to official, then it breaks > *all* buildbots, etc.Thanks, I didn't realise nobody was running a public buildbot already that built all experimental archs - though of course that makes sense. In that case I'll prioritise getting something set up. Best, Alex
On 18 August 2016 at 15:45, Alex Bradbury <asb at asbradbury.org> wrote:> Thanks, I didn't realise nobody was running a public buildbot already > that built all experimental archs - though of course that makes sense. > In that case I'll prioritise getting something set up.I just went through the previous discussions about noisy buildbots again. One of the outcomes from that discussion was the setting up of the "silent staging buildbot" at lab.llvm.org:8014/ which sounds perfect for this case. It seems to me the ideal approach would be to add a silent bot that builds RISC-V. Perhaps even better, one that builds all experimental architectures. If there's someone out there who thinks this would be useful and has spare computing power and already has a working setup to clone (i.e. the marginal cost for you of running one more buildslave is small) that would be a very welcome contribution. Otherwise, I'll try to get something set up some time in the next week or two. Best, Alex
> On Aug 18, 2016, at 8:40 AM, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 18 August 2016 at 15:45, Alex Bradbury <asb at asbradbury.org> wrote: >> Thanks, I didn't realise nobody was running a public buildbot already >> that built all experimental archs - though of course that makes sense. >> In that case I'll prioritise getting something set up. > > I just went through the previous discussions about noisy buildbots > again. One of the outcomes from that discussion was the setting up of > the "silent staging buildbot" at lab.llvm.org:8014/ which sounds > perfect for this case. It seems to me the ideal approach would be to > add a silent bot that builds RISC-V. Perhaps even better, one that > builds all experimental architectures.As a maintainer of your own Experimental backend, you’re likely be the only one looking at your silent bot, building all the experimental targets means that when (for instance) the AVR backend is broken by an API change, your build will fail till the AVR folks fix it. You may want to limit the number of `false positive` in build break and only build RISC instead. — Mehdi> > If there's someone out there who thinks this would be useful and has > spare computing power and already has a working setup to clone (i.e. > the marginal cost for you of running one more buildslave is small) > that would be a very welcome contribution. Otherwise, I'll try to get > something set up some time in the next week or two. > > Best, > > Alex > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev