On 4 November 2011 10:03, Gavin McDonald <ga...@16degrees.com.au> wrote: > Sebb, > > Seems we found a bug. > > The Nightly scheduler does not pick up changes on a 'reconfig' which is > what we use, but does on a 'restart'. > > There is a fix that I'll apply tomorrow.
Not sure the fix helped [1]. The last build that worked was Nov 03 04:44; subsequent builds have reverted to trying to check out the old Jakarta SVN, which does not make sense. It would help if the build system documented what it actually was using for a build, but if it does, it's not at all obvious. [1] http://ci.apache.org/builders/jmeter-nightly > Gav... > > >> -----Original Message----- >> From: Gavin McDonald [mailto:ga...@16degrees.com.au] >> Sent: Thursday, 3 November 2011 9:47 PM >> To: builds@apache.org >> Subject: RE: [buildbot] jmeter-nightly using wrong SVN location >> >> >> >> > -----Original Message----- >> > From: sebb [mailto:seb...@gmail.com] >> > Sent: Thursday, 3 November 2011 9:06 PM >> > To: builds@apache.org; ga...@16degrees.com.au >> > Subject: Re: [buildbot] jmeter-nightly using wrong SVN location >> > >> > On 3 November 2011 04:23, Gavin McDonald <ga...@16degrees.com.au> >> > wrote: >> > > >> > > >> > >> -----Original Message----- >> > >> From: sebb [mailto:seb...@gmail.com] >> > >> Sent: Thursday, 3 November 2011 1:06 PM >> > >> To: builds@apache.org >> > >> Subject: [buildbot] jmeter-nightly using wrong SVN location >> > >> >> > >> I changed the SVN location in the jmeter.conf file when it was >> > >> moved to >> > > TLP. >> > >> >> > >> The jmeter-trunk build [1] has picked it up, and works fine, but >> > >> the >> > > jmeter- >> > >> nightly build [2] still seems to be using the old SVN setting, i.e. >> > >> jakarta/jmeter/trunk rather than jmeter/trunk. >> > >> >> > >> The jmeter.conf file does not contain a reference to jakarta >> > >> anymore, so I don't understand why the builder is using stale >> information. >> > >> >> > >> I've just tried a dummy commit to see if that wakes up the builder; >> > >> but I assume that should not be necessary? >> > > >> > > Correct. >> > > >> > > Buildbot is configured in a way that allow projects to edit their >> > > own configurations. >> > > It is also sensitive to errors and protects a good configuration by >> > > not applying a bad one. All projects config files are seen as one >> > > big configuration by Buildbot, and as such if any other projects >> > > config file is incorrect it stops any other changes being applied too. >> > >> > In that case, perhaps it would make sense to send a mail to this list >> whenever >> > there is an error? >> >> No, doesn't happen often, and I usually point out or fix the errors so no > big >> deal. >> >> Gav... >> >> > >> > > I'm going to assume this is what happened in this instance; and that >> > > the other projects config file is now correct as I see your changes >> > > have now been pulled in. >> > > >> > > HTH >> > > >> > > Gav... >> > > >> > >> >> > >> [1] http://ci.apache.org/builders/jmeter-trunk >> > >> [2] http://ci.apache.org/builders/jmeter-nightly >> > > >> > > > > >
