On 3 January 2013 21:53, David Blaikie <dblaikie at gmail.com> wrote:> That's how you achieve this goal. What a buildbot does is governed by > the configuration in the zorg repository (that'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 documentation on the Zorg classes? I'll be digging it manually in the interim and will send you guys a patch to convert those two buildbots to LNT. Question: Is there any way of changing them locally BEFORE committing the change to Zorg? Or is it changing Zorg the only way to test? cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130107/6b3493ee/attachment.html>
Hi Renato, On 07/01/13 11:45, Renato Golin wrote:> On 3 January 2013 21:53, David Blaikie <dblaikie at gmail.com > <mailto:dblaikie at gmail.com>> wrote: > > That's how you achieve this goal. What a buildbot does is governed by > the configuration in the zorg repository (that's where we keep the > buildbot configuration code that is sync'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 change do you plan to make? Did you work out what the bug is? My basic worry is that it sounds like you are trying to hide the underlying issue rather than fixing it, please correct me if I'm wrong.> > Is there some PyDoc / Doxygen documentation on the Zorg classes? I'll be digging > it manually in the interim and will send you guys a patch to convert those two > buildbots to LNT. > > Question: Is there any way of changing them locally BEFORE committing the change > to Zorg? Or is it changing Zorg the only way to test?To test you need to set up your own build master. It's not that hard. Ciao, Duncan.> > cheers, > --renato > >
On 7 January 2013 14:37, Duncan Sands <baldrick at free.fr> wrote:> sorry, what change do you plan to make? Did you work out what the bug is? > My > basic worry is that it sounds like you are trying to hide the underlying > issue > rather than fixing it, please correct me if I'm wrong.Hi Duncan, There are two issues: 1. The LTO bug we found by running Livermore Loops on test-suite. I'm still trying to isolate this and will report as soon as I get a smaller test case. (I sent a tarball earlier to the list on how to reproduce it). Bugs like these will not be caught any more with the standard LNT tests, true, but there's also point 2 below... 2. Buildbots with multiple test builders, confusing and generating too much noise. LNT is not testing LTO at the moment, but David said there someone working on it right now. So, the way to go would be to have LNT on all buildbots (in the long run) testing with and without LTO (and possibly other variations), so we can have a coherent story and an easy way to reproduce errors locally. To test you need to set up your own build master. It's not that hard.>That's a good point. I'll do that. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130107/de498b31/attachment.html>