search for: lntbuilder

Hi, I am currently trying to set up new performance and regression testers for Polly and LLVM and would like to XFAIL two test cases. I am using the LNTBuilder instead of the NightlyTestBuilder out of the assumption that the LNTBuilder is the more modern solution. However, when trying to xfail test cases I realized the xfail=[] parameter of getLNTFactor is ignored. Previously this was not an issue, as LNT would automatically XFAIL test cases that failed...

...t's where we keep the > buildbot configuration code that is sync'd up to the lab.llvm.org > buildmaster). > Hi David, I had a go at Zorg after the website was back online. As far as I can tell, buildbot/osuosl/master/config/builders.py is the script that has to be changed, using LNTBuilder rather than ClangBuilder. I can see that there are only a few LNTBuilder's in use, and I don't want to break all buildbots, so I'm planning in just changing the gcc12 and gcc20 (with Duncan's permission) to make it stop failing the Livermore loops. Is there some PyDoc / Doxygen do...

On 3 January 2013 21:29, David Blaikie <dblaikie at gmail.com> wrote: > Fair enough - you could write up a patch for the zorg repository to do > this. > Wouldn't requiring every buildbot to use LNT achieve the same thing? --renato -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, Jan 3, 2013 at 1:52 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 3 January 2013 21:29, David Blaikie <dblaikie at gmail.com> wrote: >> >> Fair enough - you could write up a patch for the zorg repository to do >> this. > > > Wouldn't requiring every buildbot to use LNT achieve the same thing? That's how you achieve this goal.

...39;d up to the lab.llvm.org > <http://lab.llvm.org> > buildmaster). > > > Hi David, > > I had a go at Zorg after the website was back online. > > As far as I can tell, buildbot/osuosl/master/config/builders.py is the script > that has to be changed, using LNTBuilder rather than ClangBuilder. > > I can see that there are only a few LNTBuilder's in use, and I don't want to > break all buildbots, so I'm planning in just changing the gcc12 and gcc20 (with > Duncan's permission) to make it stop failing the Livermore loops. sorry, what c...

...obably be in order. > > I can have a look at the script. Would be great if you could tell me where > I can find the basic stuff. ;) > The buildbot scripts are in the 'zorg' repo, the one in question is here: http://llvm.org/viewvc/llvm-project/zorg/trunk/zorg/buildbot/builders/LNTBuilder.py?view=log - Daniel cheers, > --renato > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130422/ad78b244/attachment.html>

On 22 April 2013 18:02, Daniel Dunbar <daniel at zuster.org> wrote: > Ok, so we are already downloading from a private server (lab.llvm.org), > which IMHO we should be doing because we want tight control over the > dependencies etc. > Agreed. I forgot that your machine is outside the lab, so that may be involved > here. I don't fully understand the networking setup but

On Mon, Apr 22, 2013 at 8:00 AM, Renato Golin <renato.golin at linaro.org>wrote: > Ping? > > This is getting as often as every other run... Is that process downloading > from an internal server? If not, should we? If yes, should we not? > Ok, so we are already downloading from a private server (lab.llvm.org), which IMHO we should be doing because we want tight control over

Chandler Carruth <chandlerc at gmail.com> wrote: > I've been working to revive the PPC64 build bots, and succeeded, but > not for the right reasons. There were still bootstrap assertion > failures and other pretty blatant errors. Then we figured out why: > the Clang bootstrapping build bots for Power7 are not actually > running any of the Clang tests! > > Could one

Hey Galina, Will; I've been working to revive the PPC64 build bots, and succeeded, but not for the right reasons. There were still bootstrap assertion failures and other pretty blatant errors. Then we figured out why: the Clang bootstrapping build bots for Power7 are not actually running any of the Clang tests! Could one of you tweak this build bot's configuration to match the other