From noreply at github.com Thu Feb 2 17:45:12 2012 From: noreply at github.com (GitHub) Date: Thu, 02 Feb 2012 09:45:12 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] aa0f08: Fix typo s/Sumple/Simple/ Message-ID: <4f2acba8d8e73_3cba3f96ea30e2f4475c0@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: aa0f088b57104c906c1a17b94ebbb75a507ed100 https://github.com/buildbot/buildbot/commit/aa0f088b57104c906c1a17b94ebbb75a507ed100 Author: Amar Takhar Date: 2012-02-02 (Thu, 02 Feb 2012) Changed paths: M slave/buildslave/runprocess.py Log Message: ----------- Fix typo s/Sumple/Simple/ This has been driving me bonkers all day. Commit: c76684e39f8f2090147ce584caee51b20a15a890 https://github.com/buildbot/buildbot/commit/c76684e39f8f2090147ce584caee51b20a15a890 Author: Amar Takhar Date: 2012-02-02 (Thu, 02 Feb 2012) Changed paths: M master/setup.py Log Message: ----------- Merge remote-tracking branch 'upstream/master' Compare: https://github.com/buildbot/buildbot/compare/093f897...c76684e From nobody at buildbot.net Fri Feb 3 00:13:29 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 03 Feb 2012 00:13:29 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: Fioricet COD - How to Know Caffeine Relief for Migraines Message-ID: <045.c4fb95fdd0424348f9d74fef8cb2aad0@buildbot.net> #2190: Fioricet COD - How to Know Caffeine Relief for Migraines --------------------------+-------------------------- Reporter: fioricetCOD22 | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: Fioricet COD --------------------------+-------------------------- [[Image(https://lh6.googleusercontent.com/-y8z- rt9ZxpY/S1TsvN2txXI/AAAAAAAAYvg/ek29H3V5mw0/s512/numbers-pill.jpg)]] Migraine and other chronic headaches are the most common problem that many people are facing these days. People that has migraines usually have throbbing pain on sides of the head and oftentimes experience great sensitivity to light and even sounds. Most of the people that has migraine headaches often experience nausea dizziness. There are already several types of medication and new remedies to cure migraines and other chronic headaches. The '''[http://www.medsmd.com/fioricet.html Fioricet COD]''' is a '''prescription''' drug which is one of the commonly used '''medication''' for different types of headaches. [[Image(https://lh4.googleusercontent.com/-FDvhAnDGKEU/SIedAUlbW5I/AAAAAAAAAUE/WsRXFlFJedg/s275/PILLS.jpg)]] The caffeine is one of the three ingredients that can be found on the '''[http://www.medsmd.com/fioricet.html Fioricet]'''. The caffeine is one of the most effective way to use for migraines and other chronic headaches. The caffeine usually narrows blood vessels that restricts blood flow. The migraine '''medication''' with caffeine is an effective way to use but also has several types of side '''effects''' which can be harmful when a person use it on a high dose. [[Image(https://lh6.googleusercontent.com/-R5GrVvzKqq0/SbU8oPvMuFI/AAAAAAAAGvs /_Xo-jD2jXjY/s275/20070627f-Pills.png)]] Fioricet COD All you need to know to make indy docs . 5 places left on course by fab McLibel Director this w'end Anti-jokes >>> yung feeling ng na-tinik. XD MEEP meeeep meeep meeeep meep Meeep meep meep meep meeep meep meep meeeeeep meep meeeeeep - Photoset: Despite losing his Williams drive to Bruno Senna, Rubens Barrichello has insisted that his time in motor racing ... Just cleaned out the fridge, freezer, and pantry. Amazing how much junk + empty containers you can accumulate without even realizing it. ?Qu? lindo d?a de sol! At the pal. Haven't been here in longest time. Lots of memories You're gonna see me in your dreams tonight, my face is gonna haunt you all the time. On to UWI now A partir du 5 d?cembre on aura tous le Droit de r?ver gr?ce ? ! :D Heyy x Just looked at my baby bay pic... Bruhz coming to town.... I really love ur messages... :] Big gov't policies will not bring us jobs. The American people deserve a paycheck economy not a food stamp economy. ConfesionesPorSiCierrasocial media pienso que hacer la cama no sirve de nada, si me voy a volver a acostar !! RT for a chance to win this JUMBO Harry poster! (MUST be following) Picking winner Jan 5 2012, good luck! :) worldwide! *raises hand* Every interview I've done so far today they've asked me about my song with Ed Sheeran... which we haven't recorded yet wow , ten million followers . thats crazy! but , im proudd . :D Frankie your hair today :') ( live on FALEM CMG SEUS CANDANGOS Bring it on 1 2 3 or 4 Thatsmymovie A great many people think they are thinking when they are merely rearranging their prejudices. ~ William James Fioricet COD yeah def need to do australia next year. I really want to get there, hard to schedule with travel involved. teibaallamarpero mi saldo se agoto y una se?orita me dijo que el saldo de mi amigo tambien =O perfei??o > lindo > bonito > feio > horr?vel > desgra?a > monstro > aberra??o > coisa de outro mundo > eu TWFanmily go get following < Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 3 08:03:31 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 03 Feb 2012 08:03:31 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: 1 Message-ID: <041.7ea4500eade43f96863f7a0e21bf3ad2@buildbot.net> #2190: 1 ----------------------+--------------------- Reporter: realsugar | Owner: 1 Type: task | Status: new Priority: minor | Milestone: ongoing Version: 0.8.5 | Keywords: 1 ----------------------+--------------------- [[Image(http://www.muskul.ru/wp-content/uploads/2011/07/big_4472.jpg)]] dsdsd -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 3 08:09:36 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 03 Feb 2012 08:09:36 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: 1 Message-ID: <041.7ea4500eade43f96863f7a0e21bf3ad2@buildbot.net> #2190: 1 ----------------------+----------------------- Reporter: realsugar | Owner: 1 Type: undecided | Status: new Priority: minor | Milestone: undecided Version: 0.8.5 | Keywords: 1 ----------------------+----------------------- [[Image(http://www.muskul.ru/wp-content/uploads/2011/07/big_4472.jpg)]] 2323232323'''''''' -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 3 08:14:52 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 03 Feb 2012 08:14:52 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: 1 Message-ID: <041.7ea4500eade43f96863f7a0e21bf3ad2@buildbot.net> #2190: 1 ----------------------+----------------------- Reporter: realsugar | Owner: 1 Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: 1 ----------------------+----------------------- [[Image(http://www.muskul.ru/wp-content/uploads/2011/07/big_4472.jpg)]] 5566585 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 3 08:15:25 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 03 Feb 2012 08:15:25 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: 1 In-Reply-To: <041.7ea4500eade43f96863f7a0e21bf3ad2@buildbot.net> References: <041.7ea4500eade43f96863f7a0e21bf3ad2@buildbot.net> Message-ID: <056.068c877a030f97b4e40152a6c5dad480@buildbot.net> #2190: 1 ----------------------+------------------------ Reporter: realsugar | Owner: 1 Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: 1 | ----------------------+------------------------ Comment (by realsugar): 5445 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 00:14:35 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 00:14:35 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message Message-ID: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> #2190: MailNotifier fails to send message ----------------------+----------------------- Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Keywords: mail ----------------------+----------------------- 2012-02-03 16:10:16-0800 [-] Exception caught notifying of buildFinished event 2012-02-03 16:10:16-0800 [-] Unhandled Error Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/buildbot-0.8.5_384_gc76684e-py2.7.egg/buildbot/status/build.py", line 285, in buildFinished w.callback(self) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/Twisted-11.1.0-py2.7-macosx-10.6-intel.egg/twisted/internet/defe r.py", line 362, in callback self._startRunCallbacks(result) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/Twisted-11.1.0-py2.7-macosx-10.6-intel.egg/twisted/internet/defe r.py", line 458, in _startRunCallbacks self._runCallbacks() File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/Twisted-11.1.0-py2.7-macosx-10.6-intel.egg/twisted/internet/defe r.py", line 545, in _runCallbacks current.result = callback(current.result, *args, **kw) --- --- File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/buildbot-0.8.5_384_gc76684e-py2.7.egg/buildbot/status/builder.py ", line 512, in _buildFinished w.buildFinished(name, s, results) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/buildbot-0.8.5_384_gc76684e-py2.7.egg/buildbot/status/mail.py", line 430, in buildFinished return self.buildMessage(name, [build], results) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/buildbot-0.8.5_384_gc76684e-py2.7.egg/buildbot/status/mail.py", line 649, in buildMessage d = self.useUsers(build) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/buildbot-0.8.5_384_gc76684e-py2.7.egg/buildbot/status/mail.py", line 668, in useUsers d = self.parent.db.changes.getChangeUids(change.number) exceptions.AttributeError: 'NoneType' object has no attribute 'changes' -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 00:35:20 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 00:35:20 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.206308e92f522fa231b7feb66231d98d@buildbot.net> #2190: MailNotifier fails to send message ----------------------+------------------------ Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Resolution: Keywords: mail | ----------------------+------------------------ Comment (by tom.prince): Did you happen to reconfigure about the time this occured? It looks like self.parent is None here, so my guess as to what happend is 1. MailNotifier was triggered 2. MailNotifier blocks 3. master is reconfigured, removing MailNotifier from master 4. MailNotifier resumes, with self.parent = None 5. This error is triggered. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 01:05:20 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 01:05:20 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.83a2ca70d45d9e20232f412530691432@buildbot.net> #2190: MailNotifier fails to send message ----------------------+------------------------ Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Resolution: Keywords: mail | ----------------------+------------------------ Comment (by kevbroch): Just tried it again and didn't touch anything while the build was going. I only get this failure when I cfg MailNotifier for: mode='failing', -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 01:08:15 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 01:08:15 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.0d24ca238e07432cdd7b03e3ad0adffb@buildbot.net> #2190: MailNotifier fails to send message ----------------------+------------------------ Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Resolution: Keywords: mail | ----------------------+------------------------ Comment (by tom.prince): Can you attach the twistd.log? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 18:34:48 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 18:34:48 -0000 Subject: [Buildbot-commits] [Buildbot] #2185: GerritChangeSource: owner email can be missing In-Reply-To: <039.707d8b986e252d06445abb3b8223c4d3@buildbot.net> References: <039.707d8b986e252d06445abb3b8223c4d3@buildbot.net> Message-ID: <054.7fcb7798b0c1b8203ee26fe257403506@buildbot.net> #2185: GerritChangeSource: owner email can be missing --------------------+-------------------- Reporter: sanxiyn | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: gerrit | --------------------+-------------------- Changes (by dustin): * milestone: undecided => 0.8.+ Comment: Do you think you could write up a patch and/or test case? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 18:48:25 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 18:48:25 -0000 Subject: [Buildbot-commits] [Buildbot] #2189: buildbot upgrade-master should refuse to run, with a running master. In-Reply-To: <042.dac33b22b01f1a47787ecf254636d309@buildbot.net> References: <042.dac33b22b01f1a47787ecf254636d309@buildbot.net> Message-ID: <057.d4ead5a571abadd351e5c03ad26349b5@buildbot.net> #2189: buildbot upgrade-master should refuse to run, with a running master. -----------------------+-------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: trivial | Milestone: 0.8.6 Version: master | Resolution: Keywords: | -----------------------+-------------------- Changes (by dustin): * milestone: undecided => 0.8.6 Comment: I can see how this would be bad! -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 4 18:50:43 2012 From: noreply at github.com (GitHub) Date: Sat, 04 Feb 2012 10:50:43 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 41fead: Document the lack of auth in github hook Message-ID: <4f2d7e02f3e26_5aa83fb808c4e2f812744a@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 41feadd8e4dd4a1c911ae82655c06be2f3191689 https://github.com/buildbot/buildbot/commit/41feadd8e4dd4a1c911ae82655c06be2f3191689 Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: M master/docs/manual/cfg-statustargets.rst M master/docs/release-notes.rst Log Message: ----------- Document the lack of auth in github hook Refs #2186. This does not add authentication, but at least makes its lack clear. Commit: 45f15c7b25cd89dde4f8fb31ddd49e179dbfffe6 https://github.com/buildbot/buildbot/commit/45f15c7b25cd89dde4f8fb31ddd49e179dbfffe6 Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: M slave/buildslave/runprocess.py Log Message: ----------- Merge branch 'master' of github.com:buildbot/buildbot * 'master' of github.com:buildbot/buildbot: Fix typo s/Sumple/Simple/ Compare: https://github.com/buildbot/buildbot/compare/c76684e...45f15c7 From nobody at buildbot.net Sat Feb 4 18:50:48 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 18:50:48 -0000 Subject: [Buildbot-commits] [Buildbot] #2186: github change_hook needs security by default In-Reply-To: <040.b0011a230d9ec9a00c8a78bbb647063d@buildbot.net> References: <040.b0011a230d9ec9a00c8a78bbb647063d@buildbot.net> Message-ID: <055.a70e8e2f1706df246f873daa1b74291a@buildbot.net> #2186: github change_hook needs security by default ------------------------+------------------------ Reporter: stefanha | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: github,web | ------------------------+------------------------ Comment (by Dustin J. Mitchell): Document the lack of auth in github hook Refs #2186. This does not add authentication, but at least makes its lack clear. Changeset: 41feadd8e4dd4a1c911ae82655c06be2f3191689 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 4 18:57:18 2012 From: noreply at github.com (GitHub) Date: Sat, 04 Feb 2012 10:57:18 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] c6e3c5: Check for a running master when upgrading Message-ID: <4f2d7f8e324bc_5aa83fb808c4e2f81283e6@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: c6e3c560ce6b3159b2d373c3631b9b305aba44e2 https://github.com/buildbot/buildbot/commit/c6e3c560ce6b3159b2d373c3631b9b305aba44e2 Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: M master/buildbot/scripts/runner.py Log Message: ----------- Check for a running master when upgrading This works on POSIX, at least. Fixes #2189. From nobody at buildbot.net Sat Feb 4 18:57:35 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 18:57:35 -0000 Subject: [Buildbot-commits] [Buildbot] #2189: buildbot upgrade-master should refuse to run, with a running master. In-Reply-To: <042.dac33b22b01f1a47787ecf254636d309@buildbot.net> References: <042.dac33b22b01f1a47787ecf254636d309@buildbot.net> Message-ID: <057.e8dc7643a37fc7222750f69c8329f772@buildbot.net> #2189: buildbot upgrade-master should refuse to run, with a running master. -----------------------+--------------------- Reporter: tom.prince | Owner: Type: defect | Status: closed Priority: trivial | Milestone: 0.8.6 Version: master | Resolution: fixed Keywords: | -----------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Check for a running master when upgrading This works on POSIX, at least. Fixes #2189. Changeset: c6e3c560ce6b3159b2d373c3631b9b305aba44e2 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 4 20:15:23 2012 From: noreply at github.com (GitHub) Date: Sat, 04 Feb 2012 12:15:23 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 6d822f: Document the meaning of 'project' and 'repository' Message-ID: <4f2d91db3b215_10783fc1d2f8e2f0117035@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 6d822f2dbda5a15b329e329edc071665af3cc806 https://github.com/buildbot/buildbot/commit/6d822f2dbda5a15b329e329edc071665af3cc806 Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: A master/docs/developer/definitions.rst M master/docs/developer/index.rst Log Message: ----------- Document the meaning of 'project' and 'repository' Fixes #2184. From nobody at buildbot.net Sat Feb 4 20:15:28 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 20:15:28 -0000 Subject: [Buildbot-commits] [Buildbot] #2184: hgbuildbot.py produces changes with bogus repository strings In-Reply-To: <038.16b7093fed5c08a337a60eba314b5221@buildbot.net> References: <038.16b7093fed5c08a337a60eba314b5221@buildbot.net> Message-ID: <053.ac8c48fbb6eafc8908fc7131b0307f21@buildbot.net> #2184: hgbuildbot.py produces changes with bogus repository strings --------------------+--------------------- Reporter: dustin | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: fixed Keywords: hg docs | --------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Document the meaning of 'project' and 'repository' Fixes #2184. Changeset: 6d822f2dbda5a15b329e329edc071665af3cc806 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 4 20:29:58 2012 From: noreply at github.com (GitHub) Date: Sat, 04 Feb 2012 12:29:58 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 541eb5: merge http://trac.buildbot.net/wiki/CodeStyle into... Message-ID: <4f2d95468fa69_102c3fd8298ebafc78397@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 541eb533f4147729299a3b5bef6aae1f69aa00ea https://github.com/buildbot/buildbot/commit/541eb533f4147729299a3b5bef6aae1f69aa00ea Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: M master/docs/developer/style.rst M master/docs/release-notes.rst Log Message: ----------- merge http://trac.buildbot.net/wiki/CodeStyle into dev docs From nobody at buildbot.net Sat Feb 4 20:37:09 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 20:37:09 -0000 Subject: [Buildbot-commits] [Buildbot] #1889: add a "glossary" to the buildbot docs In-Reply-To: <038.b7364e7622e4243de676aab721cf4f55@buildbot.net> References: <038.b7364e7622e4243de676aab721cf4f55@buildbot.net> Message-ID: <053.f43f2d3059596eec4e468086851fda1f@buildbot.net> #1889: add a "glossary" to the buildbot docs ------------------------+--------------------- Reporter: dustin | Owner: Type: enhancement | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.3p1 | Resolution: fixed Keywords: docs | ------------------------+--------------------- Changes (by dustin): * status: new => closed * resolution: => fixed * milestone: 0.8.+ => 0.8.6 Comment: This exists now - http://buildbot.net/buildbot/docs/latest/developer/definitions.html -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 20:54:34 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 20:54:34 -0000 Subject: [Buildbot-commits] [Buildbot] #882: pysqlite + cygwin = no UPDATE In-Reply-To: <038.eb5a3aa9b9bd43dedb1b080ab40ab1ca@buildbot.net> References: <038.eb5a3aa9b9bd43dedb1b080ab40ab1ca@buildbot.net> Message-ID: <053.f5b56f9060947703abbfdeda184d7997@buildbot.net> #882: pysqlite + cygwin = no UPDATE ------------------------+--------------------- Reporter: dustin | Owner: Type: enhancement | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.0 | Resolution: fixed Keywords: windows | ------------------------+--------------------- Changes (by dustin): * status: new => closed * resolution: => fixed * milestone: 0.8.+ => 0.8.6 Comment: And this is why we don't support Cygwin for masters. Well, not the only reason. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 20:55:33 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 20:55:33 -0000 Subject: [Buildbot-commits] [Buildbot] #919: web-requested builds should take as many properties as params In-Reply-To: <036.1229de70559cfee3dd16cca136824c4d@buildbot.net> References: <036.1229de70559cfee3dd16cca136824c4d@buildbot.net> Message-ID: <051.0598d6b475a8fde69266f376c91bc322@buildbot.net> #919: web-requested builds should take as many properties as params ------------------------+--------------------- Reporter: Pike | Owner: Type: enhancement | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.0 | Resolution: fixed Keywords: web | ------------------------+--------------------- Changes (by dustin): * status: new => closed * resolution: => fixed * milestone: 0.8.+ => 0.8.6 Comment: !ForceScheduler fixes this. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 4 21:23:13 2012 From: noreply at github.com (GitHub) Date: Sat, 04 Feb 2012 13:23:13 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 7a1439: merge RcsTerminologyCrossReference Message-ID: <4f2da1c128a8b_66bc3ff830d2faec595a6@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 7a1439e3b01fcfb03088da22a3988f422ec0b75c https://github.com/buildbot/buildbot/commit/7a1439e3b01fcfb03088da22a3988f422ec0b75c Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: M master/docs/developer/definitions.rst Log Message: ----------- merge RcsTerminologyCrossReference From noreply at github.com Sat Feb 4 23:25:20 2012 From: noreply at github.com (GitHub) Date: Sat, 04 Feb 2012 15:25:20 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 139222: Drop support for change links Message-ID: <4f2dbe602bc26_5a893fd78d061af4101546@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 139222f3d6edb052e6870789e68298ba6cd2811e https://github.com/buildbot/buildbot/commit/139222f3d6edb052e6870789e68298ba6cd2811e Author: Dustin J. Mitchell Date: 2012-02-04 (Sat, 04 Feb 2012) Changed paths: M master/buildbot/changes/changes.py M master/buildbot/changes/mail.py M master/buildbot/changes/pb.py M master/buildbot/db/changes.py A master/buildbot/db/migrate/versions/020_remove_change_links.py M master/buildbot/db/model.py M master/buildbot/master.py M master/buildbot/test/fake/fakedb.py M master/buildbot/test/integration/test_upgrade.py M master/buildbot/test/regressions/test_bad_change_properties_rows.py M master/buildbot/test/unit/test_changes_mail_CVSMaildirSource.py M master/buildbot/test/unit/test_changes_pb.py M master/buildbot/test/unit/test_db_changes.py M master/buildbot/test/unit/test_db_connector.py A master/buildbot/test/unit/test_db_migrate_versions_020_remove_change_links.py M master/buildbot/test/unit/test_db_sourcestamps.py M master/buildbot/test/unit/test_master.py M master/contrib/bitbucket_buildbot.py M master/contrib/github_buildbot.py M master/contrib/post_build_request.py M master/docs/manual/cfg-changesources.rst Log Message: ----------- Drop support for change links These were never well-defined, and were only honestly created by CVS. They are much better implemented with a revlink function on the status API. Fixes #836. From nobody at buildbot.net Sat Feb 4 23:25:25 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 23:25:25 -0000 Subject: [Buildbot-commits] [Buildbot] #836: remove Change.links In-Reply-To: <038.a71a59a6a99fb011e7f7c9ff2dbef9cd@buildbot.net> References: <038.a71a59a6a99fb011e7f7c9ff2dbef9cd@buildbot.net> Message-ID: <053.56726a5b85fb558a3c9cdcb907c54edf@buildbot.net> #836: remove Change.links --------------------------+--------------------- Reporter: dustin | Owner: Type: enhancement | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.0 | Resolution: fixed Keywords: database, web | --------------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Drop support for change links These were never well-defined, and were only honestly created by CVS. They are much better implemented with a revlink function on the status API. Fixes #836. Changeset: 139222f3d6edb052e6870789e68298ba6cd2811e -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 4 23:45:21 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 04 Feb 2012 23:45:21 -0000 Subject: [Buildbot-commits] [Buildbot] #2183: SVNPoller stops after failure In-Reply-To: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> References: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> Message-ID: <052.76ec6650c38fa11d88f3caa475c8698e@buildbot.net> #2183: SVNPoller stops after failure ---------------------+-------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | ---------------------+-------------------- Comment (by dustin): Any info? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 00:08:32 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 00:08:32 -0000 Subject: [Buildbot-commits] [Buildbot] #2181: triggerable broken with sourcestampsets In-Reply-To: <038.ea83a3efb6ac67f3a5168c5c5a0d26bc@buildbot.net> References: <038.ea83a3efb6ac67f3a5168c5c5a0d26bc@buildbot.net> Message-ID: <053.a4e65eb23e49d386acb22709ea8f0d80@buildbot.net> #2181: triggerable broken with sourcestampsets ---------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | ---------------------+-------------------- Comment (by Dustin J. Mitchell): use getSourceStampSetId in Trigger This *should* make it compatible with sourcestamp sets. Refs #2181. Changeset: 174fb3a948d859bb8c426a234248dd39e86138e7 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 00:11:02 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 00:11:02 -0000 Subject: [Buildbot-commits] [Buildbot] #2181: triggerable broken with sourcestampsets In-Reply-To: <038.ea83a3efb6ac67f3a5168c5c5a0d26bc@buildbot.net> References: <038.ea83a3efb6ac67f3a5168c5c5a0d26bc@buildbot.net> Message-ID: <053.ffa40d08c93a847c9b23b63f42454ae4@buildbot.net> #2181: triggerable broken with sourcestampsets ---------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: | ---------------------+-------------------- Changes (by dustin): * milestone: 0.8.6 => 0.8.+ Comment: I'm bumping this to 0.8.+ since I'm not sure this will fix it completely. i'd like to get Harry's input. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 00:12:40 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 00:12:40 -0000 Subject: [Buildbot-commits] [Buildbot] #2154: Master-side git source step breaks revision+shallow In-Reply-To: <036.86713fb284eb4264cef6d32314567f45@buildbot.net> References: <036.86713fb284eb4264cef6d32314567f45@buildbot.net> Message-ID: <051.a19d8fcde17026b56d8c9b972b39e080@buildbot.net> #2154: Master-side git source step breaks revision+shallow -------------------+-------------------- Reporter: Tobi | Owner: Type: defect | Status: new Priority: minor | Milestone: 0.8.+ Version: master | Resolution: Keywords: git | -------------------+-------------------- Changes (by dustin): * milestone: 0.8.6 => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 00:14:34 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 00:14:34 -0000 Subject: [Buildbot-commits] [Buildbot] #2126: buildbot try --properties=prop=value doesn't work with try_jobdir In-Reply-To: <035.99c90048ac5befbeb80a67a3e92d2cee@buildbot.net> References: <035.99c90048ac5befbeb80a67a3e92d2cee@buildbot.net> Message-ID: <050.bbe917d93fe77087a989e41380822038@buildbot.net> #2126: buildbot try --properties=prop=value doesn't work with try_jobdir ------------------------+-------------------- Reporter: gg0 | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: try, sprint | ------------------------+-------------------- Changes (by dustin): * keywords: try => try, sprint -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 00:23:53 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 00:23:53 -0000 Subject: [Buildbot-commits] [Buildbot] #2119: upgrade-master sets auto-increment counters for id fields incorrectly in postgresql In-Reply-To: <038.b0cda045808f9a229824b84613d32f05@buildbot.net> References: <038.b0cda045808f9a229824b84613d32f05@buildbot.net> Message-ID: <053.abf16fba54ea380d0293dda14569fd39@buildbot.net> #2119: upgrade-master sets auto-increment counters for id fields incorrectly in postgresql ---------------------+-------------------- Reporter: szager | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.4p1 | Resolution: Keywords: database | ---------------------+-------------------- Comment (by dustin): On second thought, I totally see why it would happen -- since all of the inserts into changes specify a changeid, the sequence isn't consulted, nextval is never called, and .. it stays at 1. So, this should have a testcase, and a solution. Both will need to be conditioned on Postgres, since this is a unique case. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 00:30:14 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 00:30:14 -0000 Subject: [Buildbot-commits] [Buildbot] #2105: Mercurial hook - exceptions.ValueError: signal only works in main thread In-Reply-To: <039.ae0e754847623a7d7fd8839cdfcb6097@buildbot.net> References: <039.ae0e754847623a7d7fd8839cdfcb6097@buildbot.net> Message-ID: <054.e32d869988f8b44ff0a1f6d3ca3ad808@buildbot.net> #2105: Mercurial hook - exceptions.ValueError: signal only works in main thread -----------------------+-------------------- Reporter: jpichon | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.4p2 | Resolution: Keywords: hg, sprint | -----------------------+-------------------- Changes (by dustin): * keywords: hg => hg, sprint * milestone: 0.8.6 => 0.8.+ Comment: The best solution would be to fire off an HTTP request to the Buildbot change hooks. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 04:35:38 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 04:35:38 -0000 Subject: [Buildbot-commits] [Buildbot] #2137: Cache slave information on master In-Reply-To: <038.f26f9ab318df9cac4be74655285c5715@buildbot.net> References: <038.f26f9ab318df9cac4be74655285c5715@buildbot.net> Message-ID: <053.e91b6aece1ae4011dbc42c0a323a5f3b@buildbot.net> #2137: Cache slave information on master ------------------------+-------------------- Reporter: tfogal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: simple | ------------------------+-------------------- Comment (by tom.prince): After a slave has first connected, the admin and info is kept, even over reconfigs. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 5 17:37:18 2012 From: noreply at github.com (GitHub) Date: Sun, 05 Feb 2012 09:37:18 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] e6d9ed: check SQLAlchemy-Migrate version while doing migra... Message-ID: <4f2ebe4e76396_2c263fd9429042f4120723@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: e6d9eddc89c43c9fb2c0da96cfd1aa3104b50e7e https://github.com/buildbot/buildbot/commit/e6d9eddc89c43c9fb2c0da96cfd1aa3104b50e7e Author: Dustin J. Mitchell Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/db/model.py Log Message: ----------- check SQLAlchemy-Migrate version while doing migrations From nobody at buildbot.net Sun Feb 5 17:43:24 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 17:43:24 -0000 Subject: [Buildbot-commits] [Buildbot] #2124: IRC oversubsribes to buildsets, logs too much In-Reply-To: <038.e3d7141541e658c55cc0f198870726b6@buildbot.net> References: <038.e3d7141541e658c55cc0f198870726b6@buildbot.net> Message-ID: <053.69f0431c6feaf13cdd4da4a10852bbfe@buildbot.net> #2124: IRC oversubsribes to buildsets, logs too much -------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: irc | -------------------+-------------------- Comment (by dustin): I think that this is occurring because the IRC client subscribes to status for each contact. So if you've had 107 people/channels that have talked to the bot, you'll have 107 contacts and 107 subscriptions. This is kinda dumb, but I'd rather fix this when reconfiguring this to use the MQ architecture, rather than now. I will, however, add some tests to the file. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 5 19:10:29 2012 From: noreply at github.com (GitHub) Date: Sun, 05 Feb 2012 11:10:29 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] a121d9: Accept strings for CommandlineUserManager's port. Message-ID: <4f2ed4256ed6e_47d83fea75e342f82778d@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: a121d91be2275203955da2f13294edfa5e336466 https://github.com/buildbot/buildbot/commit/a121d91be2275203955da2f13294edfa5e336466 Author: Tom Prince Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/process/users/manual.py M master/buildbot/test/unit/test_process_users_manual.py Log Message: ----------- Accept strings for CommandlineUserManager's port. The port is just passed to PBManager.register's portstr. This accepts arbitrary string endpoints, so don't arbitrarily limit this to ints. In particular, this allows binding to localhost. Commit: b771e0155d71411dd608d1ef1640d5cfa4768ac4 https://github.com/buildbot/buildbot/commit/b771e0155d71411dd608d1ef1640d5cfa4768ac4 Author: Tom Prince Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/status/web/auth.py Log Message: ----------- Accept lists as well as tuples for user/password pairs in webstatus. Commit: b7c7b96d19b2d8ff7e4c534bf15e69077b3ff4ce https://github.com/buildbot/buildbot/commit/b7c7b96d19b2d8ff7e4c534bf15e69077b3ff4ce Author: Tom Prince Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/status/web/templates/box_macros.html Log Message: ----------- WebStatus: Accept stepinfo parameter in step_box. This makes the template match code changes in a4206cdea8b1b113da70c4aa532613f07995a7dd. Commit: 67875cf6659464a162e3a4d46c4ccfa3d3e79c5c https://github.com/buildbot/buildbot/commit/67875cf6659464a162e3a4d46c4ccfa3d3e79c5c Author: Tom Prince Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/status/web/hooks/github.py Log Message: ----------- Remove debugging log.msg in github change hook. Commit: 4ae1ccce5a880deb5e9a2bdb273b15dededd190e https://github.com/buildbot/buildbot/commit/4ae1ccce5a880deb5e9a2bdb273b15dededd190e Author: Tom Prince Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/db/model.py Log Message: ----------- Merge branch 'master' of git://github.com/buildbot/buildbot Compare: https://github.com/buildbot/buildbot/compare/e6d9edd...4ae1ccc From noreply at github.com Sun Feb 5 22:09:14 2012 From: noreply at github.com (GitHub) Date: Sun, 05 Feb 2012 14:09:14 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 4e6d50: Add tests for IRC client (with some minor refactor... Message-ID: <4f2efe0ae6c_27663f9e289d8af4518a@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 4e6d50880aeb796e8bef21fc8c7e674277c9394b https://github.com/buildbot/buildbot/commit/4e6d50880aeb796e8bef21fc8c7e674277c9394b Author: Dustin J. Mitchell Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/status/words.py A master/buildbot/test/unit/test_status_words.py Log Message: ----------- Add tests for IRC client (with some minor refactors) From nobody at buildbot.net Sun Feb 5 22:13:06 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 22:13:06 -0000 Subject: [Buildbot-commits] [Buildbot] #2011: Traceback popping from empty deque in addChange In-Reply-To: <043.d8d65df3cbcab5d1c78890f8f371eff1@buildbot.net> References: <043.d8d65df3cbcab5d1c78890f8f371eff1@buildbot.net> Message-ID: <058.042bf10a398cd49d90231b275b3dc9ef@buildbot.net> #2011: Traceback popping from empty deque in addChange ------------------------+------------------------- Reporter: adamcollard | Owner: Type: defect | Status: closed Priority: blocker | Milestone: 0.8.5 Version: 0.8.4p1 | Resolution: worksforme Keywords: | ------------------------+------------------------- Comment (by dustin): I haven't heard of any more LRU problems. I added fuzzing in commit 5a7db46cf113255e75e8d1110846c73746d91bb4, and I ran it for several thousand iterations without any failures. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 22:14:25 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 22:14:25 -0000 Subject: [Buildbot-commits] [Buildbot] #2191: Run fuzz tests on buildslaves Message-ID: <038.6e9d4c8bd4cf3862985946c16821da60@buildbot.net> #2191: Run fuzz tests on buildslaves -------------------+--------------------- Reporter: dustin | Owner: dustin Type: task | Status: new Priority: major | Milestone: ongoing Version: 0.8.5 | Keywords: -------------------+--------------------- With the addition of some fuzz tests, we should set up a way for the metabuildbot to automatically run them frequently on acceptable buildslaves. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 5 22:16:14 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 05 Feb 2012 22:16:14 -0000 Subject: [Buildbot-commits] [Buildbot] #2191: Run fuzz tests on buildslaves In-Reply-To: <038.6e9d4c8bd4cf3862985946c16821da60@buildbot.net> References: <038.6e9d4c8bd4cf3862985946c16821da60@buildbot.net> Message-ID: <053.9e516c14259eb9aa02af8adb06003fef@buildbot.net> #2191: Run fuzz tests on buildslaves -------------------+---------------------- Reporter: dustin | Owner: dustin Type: task | Status: new Priority: major | Milestone: ongoing Version: 0.8.5 | Resolution: Keywords: | -------------------+---------------------- Comment (by Dustin J. Mitchell): Merge branch 'fuzz' Refs #2191. * fuzz: LRU fuzzer Changeset: 47dbc3c13ddc760a0ebcf4cb43e9eae1922c536f -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 6 02:28:20 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 06 Feb 2012 02:28:20 -0000 Subject: [Buildbot-commits] [Buildbot] #2124: IRC oversubsribes to buildsets, logs too much In-Reply-To: <038.e3d7141541e658c55cc0f198870726b6@buildbot.net> References: <038.e3d7141541e658c55cc0f198870726b6@buildbot.net> Message-ID: <053.f00f2559755df7a2d9ac7601d132d1c8@buildbot.net> #2124: IRC oversubsribes to buildsets, logs too much -------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: irc | -------------------+-------------------- Changes (by dustin): * milestone: 0.8.6 => 0.8.+ Comment: (Some) tests added: {{{ commit 4e6d50880aeb796e8bef21fc8c7e674277c9394b Author: Dustin J. Mitchell Date: Sun Feb 5 16:06:26 2012 -0600 Add tests for IRC client (with some minor refactors) }}} -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 6 05:19:32 2012 From: noreply at github.com (GitHub) Date: Sun, 05 Feb 2012 21:19:32 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 7cd9a5: SVN: Import modules we actually use, rather than j... Message-ID: <4f2f62e4bec83_5f153fec1033c2f01173da@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 7cd9a58600c4959265ce43293e2b22bb63dd5d65 https://github.com/buildbot/buildbot/commit/7cd9a58600c4959265ce43293e2b22bb63dd5d65 Author: Tom Prince Date: 2012-02-05 (Sun, 05 Feb 2012) Changed paths: M master/buildbot/steps/source/svn.py Log Message: ----------- SVN: Import modules we actually use, rather than just xml. The tests fail for me, if run individually without this. From nobody at buildbot.net Mon Feb 6 12:42:33 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 06 Feb 2012 12:42:33 -0000 Subject: [Buildbot-commits] [Buildbot] #2192: GerritChangeSource: event filter Message-ID: <039.932060cedd125e5e24c932433e1fe070@buildbot.net> #2192: GerritChangeSource: event filter ------------------------+----------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: gerrit ------------------------+----------------------- You may be interested in only a small number of projects in a large Gerrit installation. This patch lets you to create Changes only for Gerrit events you care about. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 6 14:49:58 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 06 Feb 2012 14:49:58 -0000 Subject: [Buildbot-commits] [Buildbot] #2192: GerritChangeSource: event filter In-Reply-To: <039.932060cedd125e5e24c932433e1fe070@buildbot.net> References: <039.932060cedd125e5e24c932433e1fe070@buildbot.net> Message-ID: <054.16fe5ae48a982901040c7771615fd39f@buildbot.net> #2192: GerritChangeSource: event filter ------------------------+------------------------ Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: gerrit | ------------------------+------------------------ Comment (by tom.prince): I can see how this could be useful for large Gerrit installations, even though we can already filter changes at the scheduler. If something like this was going to go in, reusing the changefilter from there would make sense. In addition, even though it is perhaps mostly useful for gerrit, it seems like it would be straightforward to add this ability to all change sources at once. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 6 15:08:26 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 06 Feb 2012 15:08:26 -0000 Subject: [Buildbot-commits] [Buildbot] #2193: JSON interface / docs improvement Message-ID: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> #2193: JSON interface / docs improvement ------------------------+-------------------------- Reporter: unexist | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: json, xmlrpc ------------------------+-------------------------- I need to update my redmine plugin for buildbot, that still uses the old XMLRPC interface. Previously, with getAllBuildsInInterval I could fetch the newest builds without querying the names of the slaves first. With the JSON interface, I need to do that: Basically parse and compare longs lists and request multiple items. (slaves list, builds per slave) Is there any chance for improvement the JSON API and e.g. allow a list of builds, that can be narrowed down with select? Additionally, proper docs what select can do would be appreciated. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 6 15:11:02 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 06 Feb 2012 15:11:02 -0000 Subject: [Buildbot-commits] [Buildbot] #2193: JSON interface / docs improvement In-Reply-To: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> References: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> Message-ID: <054.ea6d55fb18dad598da869447140b449b@buildbot.net> #2193: JSON interface / docs improvement ------------------------+-------------------- Reporter: unexist | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Resolution: Keywords: | ------------------------+-------------------- Changes (by dustin): * keywords: json, xmlrpc => * milestone: undecided => 0.9.0 Comment: We'll be getting a new JSON interface soon, and having status in a DB will allow querying builds more flexibly. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 6 15:50:00 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 06 Feb 2012 15:50:00 -0000 Subject: [Buildbot-commits] [Buildbot] #2192: GerritChangeSource: event filter In-Reply-To: <039.932060cedd125e5e24c932433e1fe070@buildbot.net> References: <039.932060cedd125e5e24c932433e1fe070@buildbot.net> Message-ID: <054.dba4035d2dd4d17aa6b20072fbf13843@buildbot.net> #2192: GerritChangeSource: event filter ------------------------+------------------------ Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: gerrit | ------------------------+------------------------ Comment (by sanxiyn): I actually think a better way to do this is to create a new Gerrit user who can access only those projects and branches, so that gerrit stream- events will stream only those events. The trouble is that it can be difficult to convince Gerrit administrators that a new Gerrit user with a new set of permissions should be created. So I don't think this is a best practice, but hopefully it can help others in a similar situation. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 6 15:50:43 2012 From: noreply at github.com (GitHub) Date: Mon, 06 Feb 2012 07:50:43 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] be28d2: Default hgbuildbot.baseurl to web.baseurl Message-ID: <4f2ff6d3da887_73d93fc732a15afc1262e5@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: be28d2893a5523cdb1e4293819690b45900355dc https://github.com/buildbot/buildbot/commit/be28d2893a5523cdb1e4293819690b45900355dc Author: Dustin J. Mitchell Date: 2012-02-06 (Mon, 06 Feb 2012) Changed paths: M master/buildbot/changes/hgbuildbot.py M master/docs/manual/cfg-changesources.rst M master/docs/release-notes.rst Log Message: ----------- Default hgbuildbot.baseurl to web.baseurl web.baseurl is a common mercurial setting, so it makes sense as a default in this case. This is a non-compatible change, and is described as such in the notes. From nobody at buildbot.net Tue Feb 7 05:41:41 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 07 Feb 2012 05:41:41 -0000 Subject: [Buildbot-commits] [Buildbot] #2126: buildbot try --properties=prop=value doesn't work with try_jobdir In-Reply-To: <035.99c90048ac5befbeb80a67a3e92d2cee@buildbot.net> References: <035.99c90048ac5befbeb80a67a3e92d2cee@buildbot.net> Message-ID: <050.865bf4fbb3f299e74f6571e24fa13465@buildbot.net> #2126: buildbot try --properties=prop=value doesn't work with try_jobdir ------------------------+-------------------- Reporter: gg0 | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: try, sprint | ------------------------+-------------------- Changes (by dustin): * milestone: 0.8.6 => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 7 05:48:22 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 07 Feb 2012 05:48:22 -0000 Subject: [Buildbot-commits] [Buildbot] #2132: Builder status in waterfall not updated In-Reply-To: <041.4a880c39b94b8731b1b9377f4a70dea4@buildbot.net> References: <041.4a880c39b94b8731b1b9377f4a70dea4@buildbot.net> Message-ID: <056.28fb80d4578d386119e36934d774a783@buildbot.net> #2132: Builder status in waterfall not updated ----------------------+-------------------- Reporter: homer5439 | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: status | ----------------------+-------------------- Changes (by dustin): * milestone: 0.8.6 => 0.8.+ Comment: Let's see if we still see this behavior in 0.8.6. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Tue Feb 7 21:40:04 2012 From: noreply at github.com (GitHub) Date: Tue, 07 Feb 2012 13:40:04 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] b59cb9: fix incorrect use of bogus key c['changes'] Message-ID: <4f319a3464cb9_72b43fb8c32d72f444415a@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: b59cb9342a700896ab313db178a9fdf34a4ca7b6 https://github.com/buildbot/buildbot/commit/b59cb9342a700896ab313db178a9fdf34a4ca7b6 Author: Dustin J. Mitchell Date: 2012-02-07 (Tue, 07 Feb 2012) Changed paths: M master/docs/manual/cfg-changesources.rst Log Message: ----------- fix incorrect use of bogus key c['changes'] From nobody at buildbot.net Tue Feb 7 22:42:40 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 07 Feb 2012 22:42:40 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.90150c849788ed429042ab24d0f46fac@buildbot.net> #2190: MailNotifier fails to send message ----------------------+------------------------ Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Resolution: Keywords: mail | ----------------------+------------------------ Comment (by kevbroch): I tracked this down to problem with my configuration. I have a project that builds from multiple svn repos and so I trigger my builds and define a change filter on those. Upon removing all but one of those change sources, I no longer get this exception. I imagine this is a problem with the way in which I am configuring things but have not yet figured out the proper way to go about it. Thanks for you help with debugging this. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 7 22:55:35 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 07 Feb 2012 22:55:35 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.d85530cd19b4243866a05bbfdf0ced6b@buildbot.net> #2190: MailNotifier fails to send message ----------------------+------------------------ Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Resolution: Keywords: mail | ----------------------+------------------------ Comment (by tom.prince): Can you post your config and twistd.log (here or on #twisted on freenode). If misconfiguration is triggering this, it would be better to detect it and error out, rather than throwing random exceptions. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 8 12:18:23 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 08 Feb 2012 12:18:23 -0000 Subject: [Buildbot-commits] [Buildbot] #2176: buildslave hangs trying to kill process after "1200 seconds without output" In-Reply-To: <036.b16b7bc9de52fc28c23a1d1e44d26fb4@buildbot.net> References: <036.b16b7bc9de52fc28c23a1d1e44d26fb4@buildbot.net> Message-ID: <051.3366f803c02d7fb960b20ad06b634f15@buildbot.net> #2176: buildslave hangs trying to kill process after "1200 seconds without output" --------------------+-------------------- Reporter: hjwp | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: windows | --------------------+-------------------- Comment (by callek): What windows version twisted version and how are you running your slave. Additionaly does your process that buildbot is running do anything special with processes itself? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 8 13:00:39 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 08 Feb 2012 13:00:39 -0000 Subject: [Buildbot-commits] [Buildbot] #1044: Problems to running an slave on Windows XP In-Reply-To: <040.af193039d9df894cbd298524c2187b54@buildbot.net> References: <040.af193039d9df894cbd298524c2187b54@buildbot.net> Message-ID: <055.8170f62dd6730897d081ad7ebfc560b5@buildbot.net> #1044: Problems to running an slave on Windows XP ----------------------------+---------------------- Reporter: acamargo | Owner: Type: support-request | Status: new Priority: major | Milestone: ongoing Version: 0.8.1 | Resolution: Keywords: windows | ----------------------------+---------------------- Comment (by callek): So to be clear. Pywin32 is installed for the python you are running? Manual checking via importwin32event does not throw? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 8 13:10:48 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 08 Feb 2012 13:10:48 -0000 Subject: [Buildbot-commits] [Buildbot] #744: "queued" status for dependent builders In-Reply-To: <038.4229ed7d46a2d0d12ab6c6f7e13eae52@buildbot.net> References: <038.4229ed7d46a2d0d12ab6c6f7e13eae52@buildbot.net> Message-ID: <053.ebe13e1cc0b92922f0ddc7a916ad55a2@buildbot.net> #744: "queued" status for dependent builders ------------------------+-------------------- Reporter: tfogal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.+ Version: master | Resolution: Keywords: buildcoord | ------------------------+-------------------- Comment (by callek): Reso intentional? We only want to show queued when we are SURE we want the build and no slaves are free... right? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 8 15:31:16 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 08 Feb 2012 15:31:16 -0000 Subject: [Buildbot-commits] [Buildbot] #2176: buildslave hangs trying to kill process after "1200 seconds without output" In-Reply-To: <036.b16b7bc9de52fc28c23a1d1e44d26fb4@buildbot.net> References: <036.b16b7bc9de52fc28c23a1d1e44d26fb4@buildbot.net> Message-ID: <051.dde2dde742b4e053208443c719b3f92f@buildbot.net> #2176: buildslave hangs trying to kill process after "1200 seconds without output" --------------------+-------------------- Reporter: hjwp | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: windows | --------------------+-------------------- Comment (by millenniumhand): It's Vista with Twisted 11.1.0. We start the slave using buildslave.bat on Windows startup. Not sure what you mean by "anything special", but in some cases, we forcibly kill chrome, firefox and chromedriver because sometimes they stay running and then buildbot doesn't recognise that the test run has finished. As an interim measure, I added a check in runprocess.py so that it doesn't try to kill the process if its pid is 'None'. I didn't spend much time investigating how the pid could be 'None', though. It seems to be working fine with the patch. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 8 16:07:29 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 08 Feb 2012 16:07:29 -0000 Subject: [Buildbot-commits] [Buildbot] #2176: buildslave hangs trying to kill process after "1200 seconds without output" In-Reply-To: <036.b16b7bc9de52fc28c23a1d1e44d26fb4@buildbot.net> References: <036.b16b7bc9de52fc28c23a1d1e44d26fb4@buildbot.net> Message-ID: <051.f47bdc30e5a01e80ab3bc481f20e5b57@buildbot.net> #2176: buildslave hangs trying to kill process after "1200 seconds without output" --------------------+-------------------- Reporter: hjwp | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: windows | --------------------+-------------------- Comment (by callek): Not sure what you mean by "anything special", but in some cases, we forcibly kill chrome, firefox and chromedriver because sometimes they stay running and then buildbot doesn't recognise that the test run has finished. ---- Well chrome and Firefox both do "something special", for my purposes of the question. Firefox generally restarts its process, (which can cause buildbot to lose track of the actual process you spawned, since the spawned pid !== the firefox.exe pid after a few seconds of startup) Chrome does a thing called "Job Objects" with spawned processes, (and I am not sure if they restart a main process similar to how Firefox does), but my quick-and-dirty pre-existing solution that would work for Firefox won't work if you are using chrome (or any program that uses windows "Job Objects". I have plans to *try* and tackle this windows-specific issue at some point in the next few months though.... But glad to hear you did get a solution working for you. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 8 23:22:21 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 08 Feb 2012 23:22:21 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.4cd74f357399095c67187d6e85456a99@buildbot.net> #2190: MailNotifier fails to send message ----------------------+------------------------ Reporter: kevbroch | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: master | Resolution: Keywords: mail | ----------------------+------------------------ Comment (by kevbroch): Sorry, I am unable to post config or twistd.log for my project. I've tried to duplicate the problem using other code but was unable. I have figured out my configuration problem which was that I was naming the 3 separate c['change source']s with the same name. I was then creating a ChangeFilter with that same single name. Now I am not explicitly given the change sources names nor am I using the change filter. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 08:37:56 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 08:37:56 -0000 Subject: [Buildbot-commits] [Buildbot] #891: Better BK tests In-Reply-To: <038.b2cd0b947803f158bea663784a34c052@buildbot.net> References: <038.b2cd0b947803f158bea663784a34c052@buildbot.net> Message-ID: <053.ad3b71c6edfd36b8416f3d19ec53d5bb@buildbot.net> #891: Better BK tests ------------------------+----------------------- Reporter: dustin | Owner: Type: enhancement | Status: assigned Priority: major | Milestone: 0.8.+ Version: 0.8.0 | Resolution: Keywords: bk | ------------------------+----------------------- Changes (by verm): * owner: verm => * status: new => assigned Comment: Drop ownership, I will delete this ticket if nobody steps forward to maintain BK. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 08:43:09 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 08:43:09 -0000 Subject: [Buildbot-commits] [Buildbot] #1870: Nightly scheduler should support multiple branches. (was: Nightly scheduler should support mlutple branches.) In-Reply-To: <038.7261e9ef1a73ee1acebd7cb31d7da09e@buildbot.net> References: <038.7261e9ef1a73ee1acebd7cb31d7da09e@buildbot.net> Message-ID: <053.a547c761c1113d385336da9a6df8068e@buildbot.net> #1870: Nightly scheduler should support multiple branches. ------------------------+-------------------- Reporter: dustin | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: | ------------------------+-------------------- Comment (by verm): Fix typo in title. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 08:47:05 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 08:47:05 -0000 Subject: [Buildbot-commits] [Buildbot] #1830: Add a warning for logfiles if the log file does not exist or is not found In-Reply-To: <039.372e33a57b836ef962d4796cba2c0ee3@buildbot.net> References: <039.372e33a57b836ef962d4796cba2c0ee3@buildbot.net> Message-ID: <054.ce7c5c674a064bce08fe66519dc4c217@buildbot.net> #1830: Add a warning for logfiles if the log file does not exist or is not found ------------------------+-------------------- Reporter: darshie | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.3 | Resolution: Keywords: | ------------------------+-------------------- Comment (by callek): Should this show a warning in waterfall of "log {logfilename} not found [details]" or actually be represented as if it is the logfiles contents? I think the *way* we expose this data matters, and would be relatively representative of how difficult this is to do. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 08:48:27 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 08:48:27 -0000 Subject: [Buildbot-commits] [Buildbot] #1830: Add a warning for logfiles if the log file does not exist or is not found In-Reply-To: <039.372e33a57b836ef962d4796cba2c0ee3@buildbot.net> References: <039.372e33a57b836ef962d4796cba2c0ee3@buildbot.net> Message-ID: <054.692162955aae7cb85d47b44f1b79d0b1@buildbot.net> #1830: Add a warning for logfiles if the log file does not exist or is not found ------------------------+-------------------- Reporter: darshie | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.3 | Resolution: Keywords: | ------------------------+-------------------- Comment (by verm): Expressed in the waterfall some how I would think. A 0-byte log file lets the end-user know nothing was logged anything above that may lead to the assumption the correct data was logged rather than a warning/error from buildbot. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 08:51:57 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 08:51:57 -0000 Subject: [Buildbot-commits] [Buildbot] #1019: buildbot.net isn't a good mail-sender In-Reply-To: <038.b43b22f572357e15ade829210d7884dd@buildbot.net> References: <038.b43b22f572357e15ade829210d7884dd@buildbot.net> Message-ID: <053.9184aaeb7ab2cb16d8f7eb93903f4b8e@buildbot.net> #1019: buildbot.net isn't a good mail-sender -------------------+----------------------- Reporter: dustin | Owner: verm Type: task | Status: assigned Priority: major | Milestone: ongoing Version: 0.8.1 | Resolution: Keywords: admin | -------------------+----------------------- Changes (by verm): * owner: => verm * status: new => assigned Comment: I'll take care of this once we get into our new home. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 08:52:40 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 08:52:40 -0000 Subject: [Buildbot-commits] [Buildbot] #1999: Include full filename in warnings, if known In-Reply-To: <038.f221fd663ade2a5e8f70cee6b8df17c6@buildbot.net> References: <038.f221fd663ade2a5e8f70cee6b8df17c6@buildbot.net> Message-ID: <053.2c9c6d390b444e03d9f17e83e3765e39@buildbot.net> #1999: Include full filename in warnings, if known ------------------------+-------------------- Reporter: dustin | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.4p1 | Resolution: Keywords: | ------------------------+-------------------- Comment (by callek): With the varying forms of compilers, make systems, etc. I'm not so sure that automatically fetching the dir is a useful concept. Perhaps some argument that would take a callback like "findCurrentLikelyDir(line)" returning None or a string to represent the dir to prepend to any warning data here could work... And we could provide one/a few examples of useful default callbacks. My concerns here begin with things like: * GNUMake + -jN mixing in order of enter/leave commands confusing this log and which dir a script is in. * CMake possibly having different output * Windows Cygwin/MSYS/Shell having different path formats * PyMake having a different output format for that data than GNUMake * NMake still different. * Custom Designs different than all of the above. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 11:25:51 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 11:25:51 -0000 Subject: [Buildbot-commits] [Buildbot] #2194: unable to checkout exact revision number in SVN 'full' mode Message-ID: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> #2194: unable to checkout exact revision number in SVN 'full' mode ----------------------+----------------------- Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: ----------------------+----------------------- Buildbot always fetches the HEAD without giving --revision %(number)s to the RemoteShellCommand. (this happens using source checkout on the master side method) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 11:27:19 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 11:27:19 -0000 Subject: [Buildbot-commits] [Buildbot] #2193: JSON interface / docs improvement In-Reply-To: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> References: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> Message-ID: <054.a94c5b8fb518093db97feb1f56d82129@buildbot.net> #2193: JSON interface / docs improvement ------------------------+-------------------- Reporter: unexist | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Resolution: Keywords: | ------------------------+-------------------- Changes (by doh): * cc: rusyanov@? (added) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 11:43:19 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 11:43:19 -0000 Subject: [Buildbot-commits] [Buildbot] #2194: unable to checkout exact revision number in SVN 'full' mode In-Reply-To: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> References: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> Message-ID: <050.5f02b9982da0ed0326aeb96741828d6c@buildbot.net> #2194: unable to checkout exact revision number in SVN 'full' mode ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by doh): An example of what is desired: https://github.com/Callek/buildbot/commit/45c8150fa71bf5000f2e40b310c42a8f520a2bf5 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 11:44:37 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 11:44:37 -0000 Subject: [Buildbot-commits] [Buildbot] #2194: unable to checkout exact revision number in SVN 'full' mode In-Reply-To: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> References: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> Message-ID: <050.d8daf2749a44fa0a7ea27ca80ee4a93a@buildbot.net> #2194: unable to checkout exact revision number in SVN 'full' mode ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by callek): Note before I submit that as a pull request I'll have to peek into the docs of both SVN and buildbot again, but I will plan on doing so. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Thu Feb 9 16:12:41 2012 From: noreply at github.com (GitHub) Date: Thu, 09 Feb 2012 08:12:41 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] b75d58: don't imply that contrib modules can be imported Message-ID: <4f33f0795144_5baa1cf9ae4162027@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: b75d58c4ccc3b50a8088c70fc4ad5c80263e33f5 https://github.com/buildbot/buildbot/commit/b75d58c4ccc3b50a8088c70fc4ad5c80263e33f5 Author: Dustin J. Mitchell Date: 2012-02-09 (Thu, 09 Feb 2012) Changed paths: M master/docs/manual/cfg-changesources.rst Log Message: ----------- don't imply that contrib modules can be imported From nobody at buildbot.net Thu Feb 9 23:41:15 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 23:41:15 -0000 Subject: [Buildbot-commits] [Buildbot] #2195: two reconfigs required for new schedulers Message-ID: <038.0d445bd606c4fd69ddd734e24a307454@buildbot.net> #2195: two reconfigs required for new schedulers -------------------+------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: master | Keywords: -------------------+------------------- If you add new schedulers and builders for them at the same time, you need to reconfig twice: {{{ (sandbox)buildbot at ds0210:~/metabuildbot/metabbotcfg$ buildbot reconfig ~/metabuildbot/ sending SIGHUP to process 32287 2012-02-10 00:39:08+0100 [-] beginning configuration update 2012-02-10 00:39:08+0100 [-] Loading configuration from '/home/buildbot/metabuildbot/master.cfg' 2012-02-10 00:39:08+0100 [-] WARNING: the name 'Scheduler' is deprecated; use buildbot.schedulers.basic.SingleBranchScheduler instead (note that this may require you to change your import statement) 2012-02-10 00:39:08+0100 [-] Notify events {'successToFailure': 1, 'failureToSuccess': 1} 2012-02-10 00:39:08+0100 [-] builder(s) slave-tomprince-hermes-gentoo-1, pypy17-tw1100, pypy17-tw0900, pypy18-tw0810, pypy17-tw0820, pypy18-tw1100, pypy18-tw1020, pypy17-tw1020, pypy18-tw0820, pypy17-tw0810, pypy18-tw0900 have no schedulers to drive them 2012-02-10 00:39:08+0100 [-] reconfig aborted without making any changes Reconfiguration failed. Please inspect the master.cfg file for errors, correct them, then try 'buildbot reconfig' again. (sandbox)buildbot at ds0210:~/metabuildbot/metabbotcfg$ buildbot reconfig ~/metabuildbot/ sending SIGHUP to process 32287 2012-02-10 00:39:20+0100 [-] beginning configuration update 2012-02-10 00:39:20+0100 [-] Loading configuration from '/home/buildbot/metabuildbot/master.cfg' 2012-02-10 00:39:20+0100 [-] WARNING: the name 'Scheduler' is deprecated; use buildbot.schedulers.basic.SingleBranchScheduler instead (note that this may require you to change your import statement) 2012-02-10 00:39:20+0100 [-] Notify events {'successToFailure': 1, 'failureToSuccess': 1} 2012-02-10 00:39:20+0100 [-] adding 1 new slaves, removing 0 2012-02-10 00:39:20+0100 [-] adding 11 new builders, removing 0 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy18-tw1100/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy18-tw1100 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy18-tw0820/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy18-tw0820 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/slave-tomprince-hermes-gentoo-1/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder slave-tomprince-hermes-gentoo-1 in category slave 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy17-tw0900/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy17-tw0900 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy18-tw1020/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy18-tw1020 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy17-tw0810/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy17-tw0810 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy18-tw0810/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy18-tw0810 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy17-tw1100/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy17-tw1100 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy17-tw0820/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy17-tw0820 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy17-tw1020/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy17-tw1020 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:20+0100 [-] trying to load status pickle from /home/buildbot/metabuildbot/pypy18-tw0900/builder 2012-02-10 00:39:20+0100 [-] no saved status pickle, creating a new one 2012-02-10 00:39:20+0100 [-] added builder pypy18-tw0900 in category config 2012-02-10 00:39:20+0100 [-] [Contact] Builder added 2012-02-10 00:39:21+0100 [Broker,13,99.89.149.20] removing scheduler 'all' 2012-02-10 00:39:21+0100 [Broker,13,99.89.149.20] adding scheduler 'all' 2012-02-10 00:39:21+0100 [-] (TCP Port 8010 Closed) 2012-02-10 00:39:21+0100 [-] Stopping factory 2012-02-10 00:39:21+0100 [-] buildbot.status.web.baseweb.RotateLogSite starting on 8010 2012-02-10 00:39:21+0100 [-] Starting factory 2012-02-10 00:39:21+0100 [-] Setting up http.log rotating 10 files of 1000000 bytes each 2012-02-10 00:39:21+0100 [-] WebStatus using (/home/buildbot/metabuildbot/public_html) 2012-02-10 00:39:21+0100 [-] Starting factory 2012-02-10 00:39:21+0100 [-] configuration update complete Reconfiguration appears to have completed successfully. (sandbox)buildbot at ds0210:~/metabuildbot/metabbotcfg$ }}} This was in response to https://github.com/buildbot/metabbotcfg/pull/1/files It's on master - Buildbot version: 0.8.5-374-g5c794af. This has been the case for a few versions, but really should be fixed up before 0.8.6, given the new config interface has gone in. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 9 23:58:57 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 09 Feb 2012 23:58:57 -0000 Subject: [Buildbot-commits] [Buildbot] #2196: reconfig doesn't adopt new slaves Message-ID: <038.ec5a351e0b8b337cd2dcae9520bf017b@buildbot.net> #2196: reconfig doesn't adopt new slaves -------------------+------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Keywords: -------------------+------------------- When adding a slave in https://github.com/buildbot/metabbotcfg/pull/1/files a reconfig (or two) didn't do the trick. The slave appeared in the web UI, but twistd.log showed {{{ 2012-02-10 00:50:49+0100 [Broker,498,69.165.170.253] invalid login from user 'tomprince-hermes-gentoo-1' 2012-02-10 00:50:49+0100 [Broker,498,69.165.170.253] Peer will receive following PB traceback: 2012-02-10 00:50:49+0100 [Broker,498,69.165.170.253] Unhandled Error Traceback (most recent call last): Failure: twisted.cred.error.UnauthorizedLogin: }}} A restart fixed it. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 10 08:54:38 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 10 Feb 2012 08:54:38 -0000 Subject: [Buildbot-commits] [Buildbot] #2194: unable to checkout exact revision number in SVN 'full' mode In-Reply-To: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> References: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> Message-ID: <050.d8dd88a54741bff4a93510d41ad3aa51@buildbot.net> #2194: unable to checkout exact revision number in SVN 'full' mode -------------------+----------------------- Reporter: doh | Owner: callek Type: defect | Status: assigned Priority: major | Milestone: 0.8.6 Version: master | Resolution: Keywords: svn | -------------------+----------------------- Changes (by callek): * status: new => assigned * cc: Callek@? (added) * owner: => callek * version: 0.8.5 => master * milestone: undecided => 0.8.6 * keywords: => svn * type: undecided => defect Comment: I did a more comprehensive fix, and sent this as a pull request: https://github.com/buildbot/buildbot/pull/319 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 10 14:23:48 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 10 Feb 2012 14:23:48 -0000 Subject: [Buildbot-commits] [Buildbot] #2197: Add tests for web change_hooks. Message-ID: <042.8d180ec059bf78ad9915a6fbaf12f5ba@buildbot.net> #2197: Add tests for web change_hooks. -----------------------+------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: minor | Milestone: 0.8.+ Version: 0.8.5 | Keywords: web -----------------------+------------------- -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Fri Feb 10 14:29:11 2012 From: noreply at github.com (GitHub) Date: Fri, 10 Feb 2012 06:29:11 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] c5af51: Do not submit change links in the webhooks Message-ID: <4f3529b7876bd_72243ffd0293caf81437d7@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: c5af514957904b1e275418f8114cff74cdf5095a https://github.com/buildbot/buildbot/commit/c5af514957904b1e275418f8114cff74cdf5095a Author: Louis Opter Date: 2012-02-10 (Fri, 10 Feb 2012) Changed paths: M master/buildbot/status/web/hooks/github.py M master/buildbot/status/web/hooks/googlecode.py Log Message: ----------- Do not submit change links in the webhooks - The links argument has been removed from addChange() in changeset:139222f3d6edb052e6870789e68298ba6cd2811e (see #836); - Update/Fix the webhooks handler accordingly. Commit: ef9e5ce82aaf95d8b81632ccd94731a90950e711 https://github.com/buildbot/buildbot/commit/ef9e5ce82aaf95d8b81632ccd94731a90950e711 Author: Tom Prince Date: 2012-02-10 (Fri, 10 Feb 2012) Changed paths: M master/buildbot/status/web/hooks/base.py Log Message: ----------- Fix base and bitbucket change_hook to not pass 'links'. This was removed in 139222f3d6edb052e6870789e68298ba6cd2811e. Compare: https://github.com/buildbot/buildbot/compare/b75d58c...ef9e5ce From nobody at buildbot.net Fri Feb 10 14:29:25 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 10 Feb 2012 14:29:25 -0000 Subject: [Buildbot-commits] [Buildbot] #836: remove Change.links In-Reply-To: <038.a71a59a6a99fb011e7f7c9ff2dbef9cd@buildbot.net> References: <038.a71a59a6a99fb011e7f7c9ff2dbef9cd@buildbot.net> Message-ID: <053.60d8c41e38754f5491ea1ce0af204d3d@buildbot.net> #836: remove Change.links --------------------------+--------------------- Reporter: dustin | Owner: Type: enhancement | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.0 | Resolution: fixed Keywords: database, web | --------------------------+--------------------- Comment (by Louis Opter): Do not submit change links in the webhooks - The links argument has been removed from addChange() in changeset:139222f3d6edb052e6870789e68298ba6cd2811e (see #836); - Update/Fix the webhooks handler accordingly. Changeset: c5af514957904b1e275418f8114cff74cdf5095a -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 11 16:40:29 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 16:40:29 -0000 Subject: [Buildbot-commits] [Buildbot] #744: "queued" status for dependent builders In-Reply-To: <038.4229ed7d46a2d0d12ab6c6f7e13eae52@buildbot.net> References: <038.4229ed7d46a2d0d12ab6c6f7e13eae52@buildbot.net> Message-ID: <053.cf3c4b53af519742afe3001ba16cf5e5@buildbot.net> #744: "queued" status for dependent builders ------------------------+---------------------- Reporter: tfogal | Owner: Type: enhancement | Status: closed Priority: minor | Milestone: 0.8.+ Version: master | Resolution: wontfix Keywords: buildcoord | ------------------------+---------------------- Changes (by dustin): * status: new => closed * resolution: => wontfix Comment: Are maxBuilds or locks in use here? I suspect that what's happening is this: * sched-build gets a change, and creates a buildset with requests for all "main-*" builders * dependent scheduler attaches itself to that buildset, but this is not reflected in any status display * those builders start running -- correctly reflected in the status ("main-*" are building, "test-*" are idle) * sched-build gets another change, and creates a new, similar buildset * all builds in the first buildset complete, and the dependent scheduler creates a buildset with requests for all "test-*" builders * the next buildset in the queue is the second sched-build-created buildset, so the "main-*" builders start again, and get the slaves. At this point, "main-*" are building and "test-*" are idle. * once that's done, the master starts the "test-*" builds based on the dependent's buildset, but those immediately block on the locks preventing slave concurrency. At this point, "main-*" are busy and "test-*" are busy -- locks are not specially reflected in the build's status. It might be nice to display this differently, but I don't think that's practical at this point -- the lock logic is not very well exposed to the status. So I'm going to close as wontfix. I expect that this will look a little better in the brave new world of 0.9.x, and we can revisit the idea at that time. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 11 16:44:06 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 16:44:06 -0000 Subject: [Buildbot-commits] [Buildbot] #2190: MailNotifier fails to send message In-Reply-To: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> References: <040.e7e8e267924f1b7061b2c733e6b8351d@buildbot.net> Message-ID: <055.c282e66b953d519de564ffd610f9ba10@buildbot.net> #2190: MailNotifier fails to send message ----------------------------+------------------------ Reporter: kevbroch | Owner: Type: support-request | Status: closed Priority: major | Milestone: undecided Version: master | Resolution: fixed Keywords: mail | ----------------------------+------------------------ Changes (by dustin): * status: new => closed * type: undecided => support-request * resolution: => fixed Comment: Sounds fixed, then? Or at least, we don't have the right clues to figure out what's up. The guess in comment 1 sounds about right, and I wonder if this is some problem with lingering mailnotifiers.. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 11 16:46:23 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 16:46:23 -0000 Subject: [Buildbot-commits] [Buildbot] #2198: remove BK Message-ID: <038.d5de2e6c144f9ad358c20f1fc4cccd02@buildbot.net> #2198: remove BK -------------------+------------------- Reporter: dustin | Owner: Type: task | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Keywords: bk -------------------+------------------- BK support is in last-rites status as of 0.8.6, and should be removed in the next release. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 11 16:50:44 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 16:50:44 -0000 Subject: [Buildbot-commits] [Buildbot] #1999: Include full filename in warnings, if known In-Reply-To: <038.f221fd663ade2a5e8f70cee6b8df17c6@buildbot.net> References: <038.f221fd663ade2a5e8f70cee6b8df17c6@buildbot.net> Message-ID: <053.2f4d07f2363d1bd7bd3c0d325828c929@buildbot.net> #1999: Include full filename in warnings, if known ------------------------+-------------------- Reporter: dustin | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.4p1 | Resolution: Keywords: | ------------------------+-------------------- Comment (by dustin): Your concerns are all valid, but for the cases where it *does* work, !WarningCountingShellCommand already collects this information, so this bug is only to include that information in the output. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 11 17:00:28 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 09:00:28 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 0193b5: add news about pypy compatibility Message-ID: <4f369eac701e1_3cf71724aec564a6@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 0193b5272b0f9a163b6f9e1d8e352fa4b50facae https://github.com/buildbot/buildbot/commit/0193b5272b0f9a163b6f9e1d8e352fa4b50facae Author: Dustin J. Mitchell Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/docs/release-notes.rst Log Message: ----------- add news about pypy compatibility From noreply at github.com Sat Feb 11 17:11:04 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 09:11:04 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 8a5ee0: Revert "add news about pypy compatibility" Message-ID: <4f36a128531b4_562e3fa2b0603af0426c6@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 8a5ee081b2aaf915deea5f3285719a505237ed8d https://github.com/buildbot/buildbot/commit/8a5ee081b2aaf915deea5f3285719a505237ed8d Author: Dustin J. Mitchell Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/docs/release-notes.rst Log Message: ----------- Revert "add news about pypy compatibility" Buildbot still fails a lot of tests. I don't know what I was thinking. From nobody at buildbot.net Sat Feb 11 17:13:11 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 17:13:11 -0000 Subject: [Buildbot-commits] [Buildbot] #2195: two reconfigs required for new schedulers In-Reply-To: <038.0d445bd606c4fd69ddd734e24a307454@buildbot.net> References: <038.0d445bd606c4fd69ddd734e24a307454@buildbot.net> Message-ID: <053.2855a3d8979424dec634cb96826ae4d4@buildbot.net> #2195: two reconfigs required for new schedulers -------------------+------------------------- Reporter: dustin | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: master | Resolution: worksforme Keywords: | -------------------+------------------------- Changes (by dustin): * status: new => closed * resolution: => worksforme Comment: Ah, this was actually a problem in the metabuildbot configs -- schedulers.py was using an "old" copy of the builders variable. {{{ #! patch commit 5a5e707dc011b95b83abac70e31b654501a5d274 Author: buildbot.net admins Date: Sat Feb 11 18:12:44 2012 +0100 Don't use stale builders info to build schedulers' builderNames diff --git a/schedulers.py b/schedulers.py index 07b3676..452c443 100644 --- a/schedulers.py +++ b/schedulers.py @@ -6,14 +6,14 @@ from buildbot.schedulers.forcesched import ForceScheduler, FixedParameter, Strin from buildbot.schedulers.timed import Periodic from buildbot.schedulers.trysched import Try_Userpass from metabbotcfg.slaves import slaves -from metabbotcfg.builders import builders +from metabbotcfg import builders schedulers.append(Scheduler(name="all", branch='master', treeStableTimer=10, - builderNames=[ b['name'] for b in builders ])) + builderNames=[ b['name'] for b in builders.builders ])) schedulers.append(ForceScheduler(name="force", repository=FixedParameter(name="repository", default='git://github.com/buildbot/buildbot.git'), branch=StringParameter(name="branch", default="master"), project=FixedParameter(name="project", default=""), properties=[], - builderNames=[ b['name'] for b in builders ])) + builderNames=[ b['name'] for b in builders.builders ])) }}} -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sat Feb 11 18:35:53 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 18:35:53 -0000 Subject: [Buildbot-commits] [Buildbot] #2199: Bzr hook has hardcoded credentials Message-ID: <040.f6648217ac277301ee61533483c9159f@buildbot.net> #2199: Bzr hook has hardcoded credentials ------------------------+----------------------------- Reporter: gracinet | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: bazaar bzr hook ------------------------+----------------------------- The default name/password pair (change/changepw) is hardcoded. This is a bit surprising for someone used to, e.g., the mercurial hook, like I am. Moreover, the [http://buildbot.net/buildbot/docs/current/manual/cfg- changesources.html#chsrc-PBChangeSource general doc on PBChangeSource] says: "If you have a publicly accessible slave port, and are using PBChangeSource, you must establish a secure username and password for the change source." For consistency with Hg plugin and other Bzr hook parameters, I'd suggest to present the option in ```locations.conf``` as following: {{{ buildbot_auth = joe:secretpwd }}} (Seen both on 0.8.5 and latest git master) -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 11 18:49:40 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 10:49:40 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 32a8af: Add tests for svn revision stuff Message-ID: <4f36b844dcd9a_3f571a42ae469628@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 32a8afa43677ad7dc2b69ec819dbfac87229de1f https://github.com/buildbot/buildbot/commit/32a8afa43677ad7dc2b69ec819dbfac87229de1f Author: Justin Wood Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- Add tests for svn revision stuff Commit: 4fae8695cedd849b7d1105b5ba3aef0875ef18d5 https://github.com/buildbot/buildbot/commit/4fae8695cedd849b7d1105b5ba3aef0875ef18d5 Author: Tom Prince Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M .mailmap M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_svn.py M master/docs/manual/cfg-buildsteps.rst M master/docs/release-notes.rst Log Message: ----------- Merge pull request #319 from Callek/svn-full-clobber-revision Fixes #2194. Compare: https://github.com/buildbot/buildbot/compare/8a5ee08...4fae869 From nobody at buildbot.net Sat Feb 11 18:49:47 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 18:49:47 -0000 Subject: [Buildbot-commits] [Buildbot] #2194: unable to checkout exact revision number in SVN 'full' mode In-Reply-To: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> References: <035.74467663de0c0b63f38420171a9d5e09@buildbot.net> Message-ID: <050.f70bd0254e24830a62d1b197caccce10@buildbot.net> #2194: unable to checkout exact revision number in SVN 'full' mode -------------------+--------------------- Reporter: doh | Owner: callek Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: master | Resolution: fixed Keywords: svn | -------------------+--------------------- Changes (by Tom Prince): * status: assigned => closed * resolution: => fixed Comment: Merge pull request #319 from Callek/svn-full-clobber-revision Fixes #2194. Changeset: 4fae8695cedd849b7d1105b5ba3aef0875ef18d5 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 11 19:31:07 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 11:31:07 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] f343fe: Fix error in typo in svn_tests. Message-ID: <4f36c1fbb2215_6cc6120aae859116@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: f343fe57c4273b88be4b1ebfb29d8483d3ae13e3 https://github.com/buildbot/buildbot/commit/f343fe57c4273b88be4b1ebfb29d8483d3ae13e3 Author: Justin Wood Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- Fix error in typo in svn_tests. From noreply at github.com Sat Feb 11 20:36:42 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 12:36:42 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 27425f: assert so the hg step setup fails early in valueEr... Message-ID: <4f36d15a477f4_50253ff435a3d2fc9815d@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 27425f860e13156a1cdab5cd35866fe91d427f7b https://github.com/buildbot/buildbot/commit/27425f860e13156a1cdab5cd35866fe91d427f7b Author: Justin Wood Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/steps/source/mercurial.py Log Message: ----------- assert so the hg step setup fails early in valueError conditions Commit: adf94ee0877780d291a3f070ebaadf818747f495 https://github.com/buildbot/buildbot/commit/adf94ee0877780d291a3f070ebaadf818747f495 Author: Justin Wood Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/steps/source/mercurial.py M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_mercurial.py M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- make use of config.ConfigErrors per request from tom, and TESTS\! Commit: fa393e973d4ab9a25a9627e1ff85c3ff7f6fa5ef https://github.com/buildbot/buildbot/commit/fa393e973d4ab9a25a9627e1ff85c3ff7f6fa5ef Author: Tom Prince Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/steps/source/mercurial.py M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_mercurial.py M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- Merge pull request #321 from Callek/hg-method assert so the hg step setup fails early in valueError conditions Compare: https://github.com/buildbot/buildbot/compare/f343fe5...fa393e9 From noreply at github.com Sat Feb 11 20:38:42 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 12:38:42 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 3971cc: Merge pull request #322 from gracinet/master Message-ID: <4f36d1d1f39c3_677f3f9987483af4118a9@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 3971cc1f7df9056972b31d618cec177146c4d4e9 https://github.com/buildbot/buildbot/commit/3971cc1f7df9056972b31d618cec177146c4d4e9 Author: Tom Prince Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/contrib/bzr_buildbot.py Log Message: ----------- Merge pull request #322 from gracinet/master Fixes #2199. in Bzr hook, make user and password for PB configurable From nobody at buildbot.net Sat Feb 11 20:38:47 2012 From: nobody at buildbot.net (Buildbot) Date: Sat, 11 Feb 2012 20:38:47 -0000 Subject: [Buildbot-commits] [Buildbot] #2199: Bzr hook has hardcoded credentials In-Reply-To: <040.f6648217ac277301ee61533483c9159f@buildbot.net> References: <040.f6648217ac277301ee61533483c9159f@buildbot.net> Message-ID: <055.2c336893899da5ff6573907a510553a8@buildbot.net> #2199: Bzr hook has hardcoded credentials ----------------------------+------------------------ Reporter: gracinet | Owner: Type: enhancement | Status: closed Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: bazaar bzr hook | ----------------------------+------------------------ Changes (by Tom Prince): * status: new => closed * resolution: => fixed Comment: Merge pull request #322 from gracinet/master Fixes #2199. in Bzr hook, make user and password for PB configurable Changeset: 3971cc1f7df9056972b31d618cec177146c4d4e9 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 11 20:42:45 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 12:42:45 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] e82a1e: Fix typo. Message-ID: <4f36d2c5b0356_74c91a5eaf073479@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: e82a1e4cdd7647cc0f712c2a47af3e7d7cb7dc33 https://github.com/buildbot/buildbot/commit/e82a1e4cdd7647cc0f712c2a47af3e7d7cb7dc33 Author: Tom Prince Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/steps/source/mercurial.py M master/buildbot/steps/source/svn.py Log Message: ----------- Fix typo. From noreply at github.com Sun Feb 12 05:12:25 2012 From: noreply at github.com (GitHub) Date: Sat, 11 Feb 2012 21:12:25 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 314ded: don't add multiple logging handlers to the same lo... Message-ID: <4f374a39de3f_8cd1936aec688f8@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 314ded8b41041ba8cf75062a3465ad591a1e2308 https://github.com/buildbot/buildbot/commit/314ded8b41041ba8cf75062a3465ad591a1e2308 Author: Dustin J. Mitchell Date: 2012-02-11 (Sat, 11 Feb 2012) Changed paths: M master/buildbot/test/util/querylog.py Log Message: ----------- don't add multiple logging handlers to the same logger From nobody at buildbot.net Sun Feb 12 08:24:39 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 12 Feb 2012 08:24:39 -0000 Subject: [Buildbot-commits] [Buildbot] #2200: GitPoller should include name Message-ID: <039.c858086189affd153fd4d2d91e91b05a@buildbot.net> #2200: GitPoller should include name ------------------------+----------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: git ------------------------+----------------------- Currently GitPoller includes only email for Change's author. It should include name like git_buildbot.py does. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Sun Feb 12 12:35:37 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 12 Feb 2012 12:35:37 -0000 Subject: [Buildbot-commits] [Buildbot] #2193: JSON interface / docs improvement In-Reply-To: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> References: <039.a53c58d1bc1c9edbfa8fa6712804a185@buildbot.net> Message-ID: <054.4b73040aa55be1236eb150819a346358@buildbot.net> #2193: JSON interface / docs improvement ------------------------+-------------------- Reporter: unexist | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Resolution: Keywords: | ------------------------+-------------------- Changes (by namtabmai): * cc: andrew@? (added) -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 12 17:13:42 2012 From: noreply at github.com (GitHub) Date: Sun, 12 Feb 2012 09:13:42 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 6bc353: GitPoller: Rename _get_commit_name to _git_author_... Message-ID: <4f37f3463ab79_51f53f9a8b326af81004b4@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 6bc3531140189ef2e1ee4c779fd0cacf8e642ae4 https://github.com/buildbot/buildbot/commit/6bc3531140189ef2e1ee4c779fd0cacf8e642ae4 Author: Tom Prince Date: 2012-02-12 (Sun, 12 Feb 2012) Changed paths: M master/buildbot/changes/gitpoller.py M master/buildbot/test/unit/test_changes_gitpoller.py Log Message: ----------- GitPoller: Rename _get_commit_name to _git_author_name. We are actually getting an email here, rather than name. Commit: d7a3c0fab7e0f5bde2c214a1b312cd25a9125c8b https://github.com/buildbot/buildbot/commit/d7a3c0fab7e0f5bde2c214a1b312cd25a9125c8b Author: Tom Prince Date: 2012-02-12 (Sun, 12 Feb 2012) Changed paths: M master/buildbot/changes/gitpoller.py M master/buildbot/test/unit/test_changes_gitpoller.py Log Message: ----------- GitPoller: Include full name with author email. Compare: https://github.com/buildbot/buildbot/compare/314ded8...d7a3c0f From nobody at buildbot.net Sun Feb 12 17:14:25 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 12 Feb 2012 17:14:25 -0000 Subject: [Buildbot-commits] [Buildbot] #2200: GitPoller should include name In-Reply-To: <039.c858086189affd153fd4d2d91e91b05a@buildbot.net> References: <039.c858086189affd153fd4d2d91e91b05a@buildbot.net> Message-ID: <054.20e3a0a35f0b8e7f0246ecd5b03d03e6@buildbot.net> #2200: GitPoller should include name ------------------------+------------------------ Reporter: sanxiyn | Owner: Type: enhancement | Status: closed Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: git | ------------------------+------------------------ Changes (by tom.prince): * status: new => closed * resolution: => fixed Comment: Fixed in d7a3c0fab7e0f5bde2c214a1b312cd25a9125c8b. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 12 22:57:57 2012 From: noreply at github.com (GitHub) Date: Sun, 12 Feb 2012 14:57:57 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 76c999: don't put a BuildFactory in a variable named 'buil... Message-ID: <4f3843f5351c0_57ab13daae486985@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 76c9995c3a74af41851a984f2f41bc14c5c86799 https://github.com/buildbot/buildbot/commit/76c9995c3a74af41851a984f2f41bc14c5c86799 Author: Dustin J. Mitchell Date: 2012-02-12 (Sun, 12 Feb 2012) Changed paths: M master/docs/manual/customization.rst Log Message: ----------- don't put a BuildFactory in a variable named 'build' - that's just confusing From noreply at github.com Sun Feb 12 23:10:09 2012 From: noreply at github.com (GitHub) Date: Sun, 12 Feb 2012 15:10:09 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 3ef7a1: bow to popular pressure to use a longer variable n... Message-ID: <4f3846d1f0fcb_56da3ff7c89fd2ec9798e@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 3ef7a1e4a31c7e18a71fb57728736cae120c3475 https://github.com/buildbot/buildbot/commit/3ef7a1e4a31c7e18a71fb57728736cae120c3475 Author: Dustin J. Mitchell Date: 2012-02-12 (Sun, 12 Feb 2012) Changed paths: M master/docs/manual/customization.rst Log Message: ----------- bow to popular pressure to use a longer variable name in the docs From noreply at github.com Mon Feb 13 02:50:56 2012 From: noreply at github.com (GitHub) Date: Sun, 12 Feb 2012 18:50:56 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] d3003f: put definitions in concepts.rst Message-ID: <4f387a90cadeb_57ab13daae41070dc@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: d3003f9949c5f58cb8d00d4d9b0af3847ae5d1c6 https://github.com/buildbot/buildbot/commit/d3003f9949c5f58cb8d00d4d9b0af3847ae5d1c6 Author: Dustin J. Mitchell Date: 2012-02-12 (Sun, 12 Feb 2012) Changed paths: M master/docs/developer/definitions.rst M master/docs/manual/concepts.rst Log Message: ----------- put definitions in concepts.rst Commit: 1b7b66ddcc488b1e19ade75f6ca6d4d59f1f6f48 https://github.com/buildbot/buildbot/commit/1b7b66ddcc488b1e19ade75f6ca6d4d59f1f6f48 Author: Dustin J. Mitchell Date: 2012-02-12 (Sun, 12 Feb 2012) Changed paths: M master/docs/manual/concepts.rst Log Message: ----------- remove docs for change links Compare: https://github.com/buildbot/buildbot/compare/3ef7a1e...1b7b66d From nobody at buildbot.net Mon Feb 13 14:12:17 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 13 Feb 2012 14:12:17 -0000 Subject: [Buildbot-commits] [Buildbot] #2201: darcs failed: unrecognized option `--partial' Message-ID: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> #2201: darcs failed: unrecognized option `--partial' -------------------+----------------------- Reporter: zooko | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: darcs -------------------+----------------------- https://tahoe-lafs.org/buildbot- zfec/builders/buildbot.rubenkerkhof.com/builds/2/steps/darcs/logs/stdio This command: {{{ /usr/bin/darcs get --verbose --partial --repo-name build http://tahoe- lafs.org:6998/source/zfec/trunk }}} results in: {{{ darcs failed: unrecognized option `--partial' }}} A different builder on the same buildslave indicates that the version of darcs installed there is: {{{ darcs: 2.7.98.3 (beta 3) darcs-exact-version: darcs compiled on Jan 25 2012, at 02:09:45 Context: [TAG 2.7.98.3 Ganesh Sittampalam **20120119060551 Ignore-this: bc156878e2f54804226a43035ea5da28 ] Compiled with: array-0.3.0.2 base-4.3.1.0 bytestring-0.9.1.10 containers-0.4.0.0 directory-1.1.0.0 extensible-exceptions-0.1.1.2 filepath-1.2.0.0 hashed- storage-0.5.9 haskeline-0.6.4.6 html-1.0.1.2 mmap-0.5.7 mtl-2.0.1.0 old- time-1.0.0.6 parsec-3.1.1 process-1.0.1.5 random-1.0.0.3 regex- compat-0.95.1 tar-0.3.1.0 terminfo-0.3.2.3 text-0.11.1.5 unix-2.4.2.0 vector-0.9.1 zlib-0.5.3.1 darcs: 2.7.98.3 (beta 3) }}} I guess this means the darcs folks are finally removing the backwards- compatible {{{--partial}}} option, which was replaced by an improved {{{--lazy}}} option in darcs-2.0, released in about 2008 IIRC. Buildbot should just switch {{{--partial}}} out for {{{--lazy}}}. I don't think anybody uses darcs<2.0 anymore, and if they do they can complain, or refrain from upgrading to the newest version of buildbot. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 13 15:36:56 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 13 Feb 2012 15:36:56 -0000 Subject: [Buildbot-commits] [Buildbot] #2201: darcs failed: unrecognized option `--partial' In-Reply-To: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> References: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> Message-ID: <052.b93312422d54be37568108ef4d2429b6@buildbot.net> #2201: darcs failed: unrecognized option `--partial' -------------------+------------------------ Reporter: zooko | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: darcs | -------------------+------------------------ Comment (by dustin): To my knowledge, you're the only person using Darcs. Support is orphaned: {{{ Darcs VC S: Orphaned U: http://trac.buildbot.net/wiki/darcs }}} Do you want to take that on? I'll apply the suggested change (without testing). -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 13 15:39:15 2012 From: noreply at github.com (GitHub) Date: Mon, 13 Feb 2012 07:39:15 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 7192a0: Darcs: Replace --partial with --lazy Message-ID: <4f392ea3700f6_68833fb5e60ccafc5873a@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 7192a07492257d2104324182bbbaee6b74ef558b https://github.com/buildbot/buildbot/commit/7192a07492257d2104324182bbbaee6b74ef558b Author: Dustin J. Mitchell Date: 2012-02-13 (Mon, 13 Feb 2012) Changed paths: M slave/buildslave/commands/darcs.py M slave/buildslave/test/unit/test_commands_darcs.py Log Message: ----------- Darcs: Replace --partial with --lazy Fixes #2201. From nobody at buildbot.net Mon Feb 13 15:39:25 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 13 Feb 2012 15:39:25 -0000 Subject: [Buildbot-commits] [Buildbot] #2201: darcs failed: unrecognized option `--partial' In-Reply-To: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> References: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> Message-ID: <052.5449f75d6802ff92d732f1dc6427a294@buildbot.net> #2201: darcs failed: unrecognized option `--partial' -------------------+------------------------ Reporter: zooko | Owner: Type: defect | Status: closed Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: darcs | -------------------+------------------------ Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Darcs: Replace --partial with --lazy Fixes #2201. Changeset: 7192a07492257d2104324182bbbaee6b74ef558b -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 13 22:50:54 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 13 Feb 2012 22:50:54 -0000 Subject: [Buildbot-commits] [Buildbot] #2183: SVNPoller stops after failure In-Reply-To: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> References: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> Message-ID: <052.acc9b415ea659280f79b385a93f60960@buildbot.net> #2183: SVNPoller stops after failure ---------------------+-------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | ---------------------+-------------------- Comment (by fgsch): I checked the logs today and it has not crashed since this report. This can be closed now. I will open a new ticket should it happen again. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 13 22:52:17 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 13 Feb 2012 22:52:17 -0000 Subject: [Buildbot-commits] [Buildbot] #2202: fix deprecated warning on svnpoller Message-ID: <037.fe5c34b1fe2b9ea5e38a9b4635209601@buildbot.net> #2202: fix deprecated warning on svnpoller ------------------------+----------------------- Reporter: fgsch | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: undecided Version: 0.8.5 | Keywords: ------------------------+----------------------- see attached diff. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Tue Feb 14 00:03:20 2012 From: noreply at github.com (GitHub) Date: Mon, 13 Feb 2012 16:03:20 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] f7fb48: Get rid of internal usage of deprecated who argume... Message-ID: <4f39a4c86e217_33dd3fca41b152ec3398c@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: f7fb488a888b50507046e7717e6ac669906d1a2e https://github.com/buildbot/buildbot/commit/f7fb488a888b50507046e7717e6ac669906d1a2e Author: Tom Prince Date: 2012-02-13 (Mon, 13 Feb 2012) Changed paths: M master/buildbot/changes/mail.py M master/buildbot/changes/svnpoller.py M master/buildbot/status/web/hooks/base.py M master/buildbot/status/web/hooks/googlecode.py M master/buildbot/test/unit/test_changes_mail_CVSMaildirSource.py M master/buildbot/test/unit/test_status_web_change_hook.py M master/buildbot/test/unit/test_status_web_change_hooks_googlecode.py M master/contrib/post_build_request.py Log Message: ----------- Get rid of internal usage of deprecated who argument for addChange. The who argument has been renamed to author. Fixes #2202. From nobody at buildbot.net Tue Feb 14 00:03:27 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 00:03:27 -0000 Subject: [Buildbot-commits] [Buildbot] #2202: fix deprecated warning on svnpoller In-Reply-To: <037.fe5c34b1fe2b9ea5e38a9b4635209601@buildbot.net> References: <037.fe5c34b1fe2b9ea5e38a9b4635209601@buildbot.net> Message-ID: <052.f6dcab2f8fa20c9964f4a62946e38ffe@buildbot.net> #2202: fix deprecated warning on svnpoller ------------------------+------------------------ Reporter: fgsch | Owner: Type: enhancement | Status: closed Priority: trivial | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: | ------------------------+------------------------ Changes (by Tom Prince): * status: new => closed * resolution: => fixed Comment: Get rid of internal usage of deprecated who argument for addChange. The who argument has been renamed to author. Fixes #2202. Changeset: f7fb488a888b50507046e7717e6ac669906d1a2e -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 14 01:15:40 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 01:15:40 -0000 Subject: [Buildbot-commits] [Buildbot] #2183: SVNPoller stops after failure In-Reply-To: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> References: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> Message-ID: <052.275239b532e21a19570e0f2a5e11e708@buildbot.net> #2183: SVNPoller stops after failure ---------------------+--------------------- Reporter: fgsch | Owner: Type: defect | Status: closed Priority: critical | Milestone: 0.8.6 Version: 0.8.5 | Resolution: fixed Keywords: | ---------------------+--------------------- Changes (by dustin): * status: new => closed * resolution: => fixed Comment: Thanks! -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 14 01:15:48 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 01:15:48 -0000 Subject: [Buildbot-commits] [Buildbot] #2183: SVNPoller stops after failure In-Reply-To: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> References: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> Message-ID: <052.50f71cefd2321f897d5f70b5e80fddea@buildbot.net> #2183: SVNPoller stops after failure ---------------------+----------------------- Reporter: fgsch | Owner: Type: defect | Status: reopened Priority: critical | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | ---------------------+----------------------- Changes (by dustin): * status: closed => reopened * resolution: fixed => -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 14 01:15:59 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 01:15:59 -0000 Subject: [Buildbot-commits] [Buildbot] #2183: SVNPoller stops after failure In-Reply-To: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> References: <037.681b6161918e718d0afe485e5788d0c3@buildbot.net> Message-ID: <052.c27d9df19cbe1768d904a7e7873b32f3@buildbot.net> #2183: SVNPoller stops after failure ---------------------+------------------------- Reporter: fgsch | Owner: Type: defect | Status: closed Priority: critical | Milestone: 0.8.6 Version: 0.8.5 | Resolution: worksforme Keywords: | ---------------------+------------------------- Changes (by dustin): * status: reopened => closed * resolution: => worksforme -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 14 05:01:23 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 05:01:23 -0000 Subject: [Buildbot-commits] [Buildbot] #2201: darcs failed: unrecognized option `--partial' In-Reply-To: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> References: <037.1a32c2d6ae81cdb1eb59d383a4f7f365@buildbot.net> Message-ID: <052.cc04bbec77f83d92c14699036656dc55@buildbot.net> #2201: darcs failed: unrecognized option `--partial' -------------------+------------------------ Reporter: zooko | Owner: Type: defect | Status: closed Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: darcs | -------------------+------------------------ Comment (by zooko): Replying to [comment:1 dustin]: > Do you want to take that on? Not really -- we're moving off of it too. > I'll apply the suggested change (without testing). Thanks for the fast turnaround on https://github.com/buildbot/buildbot/commit/7192a07492257d2104324182bbbaee6b74ef558b ! :-) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 14 07:50:47 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 07:50:47 -0000 Subject: [Buildbot-commits] [Buildbot] #2203: svn copy method, timeout setting has no impact Message-ID: <035.6e064d864f152aafabd80460867793de@buildbot.net> #2203: svn copy method, timeout setting has no impact -------------------+----------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: -------------------+----------------------- Setting timeout to SVN buildstep(master side) does not influence actual timeout. It does make a copy of 'source' dir with timeout set to 120, which is quite insufficient for copying big projects. The way to solve the problem is to either add '-v' flag for 'cp' command(will not work for huge files) or make 'timeout' setting take into account. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 14 07:56:31 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 14 Feb 2012 07:56:31 -0000 Subject: [Buildbot-commits] [Buildbot] #2204: svn export method and svnversion command Message-ID: <035.b638141107775d1746aa07461755ae4f@buildbot.net> #2204: svn export method and svnversion command -------------------+----------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: -------------------+----------------------- Currently buildbot does the following with the export method of SVN source checkout(master side): * svn co proto://path/to/repository source * svn export source build * cd build && svnversion svnversion in exported directory will always fail. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 15 02:39:19 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 15 Feb 2012 02:39:19 -0000 Subject: [Buildbot-commits] [Buildbot] #2205: Change MailNotifier mode to allow for more flexibility Message-ID: <037.42131bc1fd25aa098d8a6bccefb106af@buildbot.net> #2205: Change MailNotifier mode to allow for more flexibility ------------------------+----------------------- Reporter: fgsch | Owner: Type: enhancement | Status: new Priority: minor | Milestone: undecided Version: 0.8.5 | Keywords: ------------------------+----------------------- The attached patch changes mode to be a list allowing for example to receive emails when there is a change and for any successive failures or only for warnings. The change also handles backward compatibility when passing a string and in particular for "all" and "warnings" string modes. The only change wrt to the current behaviour is that mode="all" will report whether the build failed, passed or warnings were found instead of "The Buildbot has finished a build" in the default message. I believe this is an improvement, ymmv. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 15 06:30:32 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 15 Feb 2012 06:30:32 -0000 Subject: [Buildbot-commits] [Buildbot] #2203: svn copy method, timeout setting has no impact In-Reply-To: <035.6e064d864f152aafabd80460867793de@buildbot.net> References: <035.6e064d864f152aafabd80460867793de@buildbot.net> Message-ID: <050.3974dd273b24973eb425f1dcceea1978@buildbot.net> #2203: svn copy method, timeout setting has no impact -------------------+-------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: | -------------------+-------------------- Changes (by dustin): * milestone: undecided => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 04:37:03 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 04:37:03 -0000 Subject: [Buildbot-commits] [Buildbot] #1765: rm -rf always run even if there is nothing to delete In-Reply-To: <037.6d1f99954d171596ee7f818914c1c05f@buildbot.net> References: <037.6d1f99954d171596ee7f818914c1c05f@buildbot.net> Message-ID: <052.3d508b5dfeea353afe446af575ef8c4c@buildbot.net> #1765: rm -rf always run even if there is nothing to delete ------------------------+---------------------- Reporter: fgsch | Owner: Type: enhancement | Status: closed Priority: minor | Milestone: 0.8.+ Version: 0.8.3p1 | Resolution: wontfix Keywords: svn | ------------------------+---------------------- Changes (by tom.prince): * status: new => closed * resolution: => wontfix Comment: The only time this should trigger is if the builder is the first time a given builder has run on a slave (or the first time after the mode/workdir has changed). As indicated, the extra run of 'rm -rf' is harmless in the case anyway, so it seems inadvisable to make the check more complicated to handle this case. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 04:42:23 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 04:42:23 -0000 Subject: [Buildbot-commits] [Buildbot] #2137: Store cached slave information in db (was: Cache slave information on master) In-Reply-To: <038.f26f9ab318df9cac4be74655285c5715@buildbot.net> References: <038.f26f9ab318df9cac4be74655285c5715@buildbot.net> Message-ID: <053.91a35f552f227814065df47d1fb77dfb@buildbot.net> #2137: Store cached slave information in db ------------------------+-------------------- Reporter: tfogal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: simple | ------------------------+-------------------- Changes (by tom.prince): * milestone: 0.8.6 => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Thu Feb 16 05:29:23 2012 From: noreply at github.com (GitHub) Date: Wed, 15 Feb 2012 21:29:23 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 39c427: Remove tailor from list of unknown authors. Message-ID: <4f3c943394e85_779e14faaf0120892@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 39c427ab76e6a93f835058657fa248944dc7dfa3 https://github.com/buildbot/buildbot/commit/39c427ab76e6a93f835058657fa248944dc7dfa3 Author: Tom Prince Date: 2012-02-15 (Wed, 15 Feb 2012) Changed paths: M master/CREDITS Log Message: ----------- Remove tailor from list of unknown authors. Tailor is a program for migrating vcs repositories between formats. It also appears to have been used as a name by warner for a handful of commits. From noreply at github.com Thu Feb 16 05:32:50 2012 From: noreply at github.com (GitHub) Date: Wed, 15 Feb 2012 21:32:50 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 4e7916: Update MAINTAINERS. Message-ID: <4f3c9502ad9f3_7bc53f8087650af8965e8@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 4e7916cd2fcdd45bc07ee03921913eae89e583d6 https://github.com/buildbot/buildbot/commit/4e7916cd2fcdd45bc07ee03921913eae89e583d6 Author: Tom Prince Date: 2012-02-15 (Wed, 15 Feb 2012) Changed paths: M MAINTAINERS.txt Log Message: ----------- Update MAINTAINERS. From nobody at buildbot.net Thu Feb 16 05:39:03 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 05:39:03 -0000 Subject: [Buildbot-commits] [Buildbot] #1917: improvements and docs to 'buildbot try' with DVCS In-Reply-To: <038.ddaa7ad01abaab102af543ada84c52a7@buildbot.net> References: <038.ddaa7ad01abaab102af543ada84c52a7@buildbot.net> Message-ID: <053.9a2d3d22603a58e121526c18b5ceecc2@buildbot.net> #1917: improvements and docs to 'buildbot try' with DVCS ------------------------+------------------------ Reporter: dustin | Owner: tomprince Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3p1 | Resolution: Keywords: git, try | ------------------------+------------------------ Changes (by tom.prince): * milestone: 0.8.6 => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 14:03:01 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 14:03:01 -0000 Subject: [Buildbot-commits] [Buildbot] #2204: svn export method and svnversion command In-Reply-To: <035.b638141107775d1746aa07461755ae4f@buildbot.net> References: <035.b638141107775d1746aa07461755ae4f@buildbot.net> Message-ID: <050.51c420f75a838bb59cdec3c273fbeec0@buildbot.net> #2204: svn export method and svnversion command -------------------+-------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | -------------------+-------------------- Changes (by tom.prince): * milestone: undecided => 0.8.6 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 14:14:57 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 14:14:57 -0000 Subject: [Buildbot-commits] [Buildbot] #1754: VC9 compile step assumes PlatformSDK is installed In-Reply-To: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> References: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> Message-ID: <056.e969c4d46185e6c1dbb4028885fb8400@buildbot.net> #1754: VC9 compile step assumes PlatformSDK is installed ----------------------+-------------------- Reporter: philippem | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: windows | ----------------------+-------------------- Comment (by tom.prince): I don't have access VS9, to figure out what should be done to fix this, if anything. My guess would be that it is the project that is setting those paths, rather than anything buildbot is doing. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 14:17:44 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 14:17:44 -0000 Subject: [Buildbot-commits] [Buildbot] #1055: missing a no-clobber option when svn fail to update? (and other rcs?) In-Reply-To: <038.db313d3456fca85b3d9c76021a8ec60e@buildbot.net> References: <038.db313d3456fca85b3d9c76021a8ec60e@buildbot.net> Message-ID: <053.6348be1ebdc4c4d0b77326f276538ffa@buildbot.net> #1055: missing a no-clobber option when svn fail to update? (and other rcs?) -------------------+--------------------- Reporter: blaize | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.+ Version: 0.8.2 | Resolution: fixed Keywords: svn | -------------------+--------------------- Changes (by tom.prince): * status: new => closed * resolution: => fixed Comment: This is fixed in the master-side steps. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 14:36:14 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 14:36:14 -0000 Subject: [Buildbot-commits] [Buildbot] #539: add a simpler change notification protocol In-Reply-To: <040.77cee5f32c0b6f91f372aa7f464a79d2@buildbot.net> References: <040.77cee5f32c0b6f91f372aa7f464a79d2@buildbot.net> Message-ID: <055.45b614c1b76ca61bbe9ac04f72fdf77f@buildbot.net> #539: add a simpler change notification protocol ------------------------+--------------------- Reporter: ipv6guru | Owner: Type: enhancement | Status: closed Priority: major | Milestone: 0.8.+ Version: 0.7.10 | Resolution: fixed Keywords: | ------------------------+--------------------- Changes (by tom.prince): * status: new => closed * resolution: => fixed Comment: There is a script contrib/post_build_request.py to do this. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 16 23:15:01 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 16 Feb 2012 23:15:01 -0000 Subject: [Buildbot-commits] [Buildbot] #2206: Change Hooks always return a HTTP 500 error Message-ID: <040.a9a1cc0365b3b17e98fa1ee454fac8f1@buildbot.net> #2206: Change Hooks always return a HTTP 500 error ---------------------+---------------------------------------------- Reporter: kalessin | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: master | Keywords: master, status, web, change_hook ---------------------+---------------------------------------------- Hello, I recently added support for the Google Code webhook in buildbot's change_hooks. But I noticed that even when the Google POST request is correctly parsed (and the changes correctly returned to [https://github.com/buildbot/buildbot/blob/master/master/buildbot/status/web/change_hook.py#L77 buildbot.status.web.change_hook.ChangeHookResource.getChanges]), buildbot was returning a 500 error to Google Code (then Google Code resubmits the request which triggers a lot of builds for the same revision). Here is an example: {{{ > 2012/02/16 05:36:36.576258 length=2128 from=0 to=2127 POST /change_hook/googlecode HTTP/1.1\r Google-Code-Project-Hosting-Hook-HMAC: 59721811b23b664451aad75dc8cb03ff\r Content-Type: application/json; charset=UTF-8\r User-Agent: Google Code Project Hosting (+http://code.google.com/p/support/wiki/PostCommitWebHooks)\r Host: builds.rathaxes.org:20096\r Content-Length: 1788\r Accept-Encoding: gzip\r \r {"repository_path":"https://code.google.com/p/rathaxes/","project_name":"rathaxes","revisions":[{"added":[],"parents":["8021567e5b325faf82150f85b91e49cc3e5f7aa1"],"author":"David xxxxxx \\u003Cdav.xxxxxx at gmail.com\\u003E","url":"http://rathaxes.googlecode.com /hg- history/068f44aee029127b0fc45af999b8d4c131e54fa7/","timestamp":1329355433,"message":"rathaxes: compiler: Fix the builtins and the way to manage the config matching to reflect the recent changes.","path_count":11,"removed":[],"modified":["/rathaxes/compiler/rtxLink/rtxLink_ConfigMatcher.inc.cws","/rathaxes/compiler/rtxNode/rtxNode.inc.cws","/rathaxes/compiler/rtxType/rules_types/number.inc.cws","/rathaxes/compiler/rtxType/rules_types/string.inc.cws","/rathaxes/compiler/rtxType/rules_types/symbol.inc.cws","/rathaxes/compiler/tests/03_A_test_config_match_lesser.cws","/rathaxes/compiler/tests/03_B_test_config_match_lesser_or_equal.cws","/rathaxes/compiler/tests/03_C_test_config_match_equal.cws","/rathaxes/compiler/tests/03_D_test_config_match_greater_or_equal.cws","/rathaxes/compiler/tests/03_E_test_config_match_greater.cws","/rathaxes/compiler/tests/03_F_test_config_match.cws"],"revision":"068f44aee029127b0fc45af999b8d4c131e54fa7"},{"added":[],"parents":["068f44aee029127b0fc45af999b8d4c131e54fa7","819e991f716f24a5eb7ee7ec1fb1d6f60b5f1f94"],"author":"David xxxxxx \\u003Cdav.xxxxxx at gmail.com\\u003E","url":"http://rathaxes.googlecode.com /hg- history/69e66ba52716815d2b358c22b4260234962235cf/","timestamp":1329355461,"message":"merge","path_count":3,"removed":[],"modified":["/rathaxes/compiler/rtxType/rules_types/number.inc.cws","/rathaxes/compiler/rtxType/rules_types/string.inc.cws","/rathaxes/compiler/rtxType/rules_types/symbol.inc.cws"],"revision":"69e66ba52716815d2b358c22b4260234962235cf"}],"revision_count":2} < 2012/02/16 05:36:36.598502 length=548 from=0 to=547 HTTP/1.1 500 Internal Server Error\r Date: Thu, 16 Feb 2012 05:36:36 GMT\r Content-Length: 385\r Content-Type: text/html; charset=utf-8\r Server: TwistedWeb/11.1.0\r \r 500 - Request did not return a string

Request did not return a string

Request:

<POST /change_hook/googlecode
 HTTP/1.1>

Resource:
<buildbot.status.web.change_hook.ChangeHookResource instance at
 0x2075cf8>

Value:
<Deferred at
 0x2d6cea8>

}}} I'm not familiar with Twisted at all, so I'm not sure what the problem is. Could that be something missing in [https://github.com/buildbot/buildbot/blob/master/master/buildbot/status/web/change_hook.py#L51 ChangeHookResource.render_POST] to indicate that the request is a success? Thanks -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 17 00:12:50 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 00:12:50 -0000 Subject: [Buildbot-commits] [Buildbot] #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. Message-ID: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. -----------------------+------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: master | Keywords: -----------------------+------------------- By default, MailNotifier looks up users in the database, based on the uid stored with the relevant changes. It then tries to get the email associated to that id. However, the various change sources don't populate the email attribute of users they create, so most users won't have an associated email record (even if their identifier is an email address). This can be worked around by passing lookup="" which avoids using the database. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Fri Feb 17 00:46:20 2012 From: noreply at github.com (GitHub) Date: Thu, 16 Feb 2012 16:46:20 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 2e25ec: web: Return server.NOT_DONE_YET from change_hooks. Message-ID: <4f3da35cd5b71_676b3fea0a5182fc1675b4@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 2e25ec71c0791178de84222228b147ab309b77d6 https://github.com/buildbot/buildbot/commit/2e25ec71c0791178de84222228b147ab309b77d6 Author: Tom Prince Date: 2012-02-16 (Thu, 16 Feb 2012) Changed paths: M master/buildbot/status/web/change_hook.py M master/buildbot/test/fake/web.py M master/buildbot/test/unit/test_status_web_base.py M master/buildbot/test/unit/test_status_web_change_hook.py M master/buildbot/test/unit/test_status_web_change_hooks_github.py M master/buildbot/test/unit/test_status_web_change_hooks_googlecode.py Log Message: ----------- web: Return server.NOT_DONE_YET from change_hooks. twisted.web.resource predates deferreds, and so has idiosyncratic handling of asynchronous results. Fix /change_hook handling to return proper results and add support from properly testing this in FakeRequest.test_render. Fixes #2206. From nobody at buildbot.net Fri Feb 17 00:46:27 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 00:46:27 -0000 Subject: [Buildbot-commits] [Buildbot] #2206: Change Hooks always return a HTTP 500 error In-Reply-To: <040.a9a1cc0365b3b17e98fa1ee454fac8f1@buildbot.net> References: <040.a9a1cc0365b3b17e98fa1ee454fac8f1@buildbot.net> Message-ID: <055.656443a20d23a5f1da9d57d57b7e0c20@buildbot.net> #2206: Change Hooks always return a HTTP 500 error ---------------------------------------------+------------------------ Reporter: kalessin | Owner: Type: defect | Status: closed Priority: major | Milestone: undecided Version: master | Resolution: fixed Keywords: master, status, web, change_hook | ---------------------------------------------+------------------------ Changes (by Tom Prince): * status: new => closed * resolution: => fixed Comment: web: Return server.NOT_DONE_YET from change_hooks. twisted.web.resource predates deferreds, and so has idiosyncratic handling of asynchronous results. Fix /change_hook handling to return proper results and add support from properly testing this in FakeRequest.test_render. Fixes #2206. Changeset: 2e25ec71c0791178de84222228b147ab309b77d6 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Fri Feb 17 01:01:08 2012 From: noreply at github.com (GitHub) Date: Thu, 16 Feb 2012 17:01:08 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] f0fc39: Fix pyflakes errors. Message-ID: <4f3da6d4aa182_ac014a2ae447941@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: f0fc394b448039cec21904fe19b771fcaf0e543b https://github.com/buildbot/buildbot/commit/f0fc394b448039cec21904fe19b771fcaf0e543b Author: Tom Prince Date: 2012-02-16 (Thu, 16 Feb 2012) Changed paths: M master/buildbot/status/web/change_hook.py M master/buildbot/test/unit/test_status_web_base.py M master/buildbot/test/unit/test_status_web_change_hooks_github.py M master/buildbot/test/unit/test_status_web_change_hooks_googlecode.py Log Message: ----------- Fix pyflakes errors. From nobody at buildbot.net Fri Feb 17 04:40:46 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 04:40:46 -0000 Subject: [Buildbot-commits] [Buildbot] #2208: GerritChangeSource: orphan SSH process Message-ID: <039.e5839424d89858039e6fefe38987865c@buildbot.net> #2208: GerritChangeSource: orphan SSH process --------------------+----------------------- Reporter: sanxiyn | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: gerrit --------------------+----------------------- When you stop a buildmaster using GerritChangeSource you get: {{{ [-] Received SIGTERM, shutting down. [-] starting 'gerrit stream-events' [-] Main loop terminated. [-] Server Shut Down. }}} That is, GerritChangeSource restarts 'gerrit stream-events' SSH process while the buildmaster is shutting down. This results in an orphan SSH process. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 17 05:07:08 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 05:07:08 -0000 Subject: [Buildbot-commits] [Buildbot] #2209: GerritStatusPush should be able to ignore build results Message-ID: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> #2209: GerritStatusPush should be able to ignore build results ------------------------+----------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: gerrit ------------------------+----------------------- There should be a way to ignore build results (notably RETRY). Currently a review is always sent no matter what reviewCB does, for Gerrit+Git. Attached patch lets Gerrit+Git to ignore build results if reviewCB returns None message like Gerrit+Repo does, and documents this fact. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 17 06:58:52 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 06:58:52 -0000 Subject: [Buildbot-commits] [Buildbot] #2208: GerritChangeSource: orphan SSH process In-Reply-To: <039.e5839424d89858039e6fefe38987865c@buildbot.net> References: <039.e5839424d89858039e6fefe38987865c@buildbot.net> Message-ID: <054.74c8314beb2ffe855fe24f3f8c2c7a11@buildbot.net> #2208: GerritChangeSource: orphan SSH process --------------------+------------------------ Reporter: sanxiyn | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: gerrit | --------------------+------------------------ Comment (by tom.prince): This is probably best handled by using twisted.conch to connect to the server, instead of calling out to ssh as a seperate process. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 17 06:59:25 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 06:59:25 -0000 Subject: [Buildbot-commits] [Buildbot] #2208: GerritChangeSource: orphan SSH process In-Reply-To: <039.e5839424d89858039e6fefe38987865c@buildbot.net> References: <039.e5839424d89858039e6fefe38987865c@buildbot.net> Message-ID: <054.c3fe9e0bafbcf0c639cc326951ccbf59@buildbot.net> #2208: GerritChangeSource: orphan SSH process --------------------+-------------------- Reporter: sanxiyn | Owner: Type: defect | Status: new Priority: minor | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: gerrit | --------------------+-------------------- Changes (by tom.prince): * priority: major => minor * milestone: undecided => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 17 07:16:52 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 07:16:52 -0000 Subject: [Buildbot-commits] [Buildbot] #2209: GerritStatusPush should be able to ignore build results In-Reply-To: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> References: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> Message-ID: <054.93619a69f34b8199425a88d3f3cc34e2@buildbot.net> #2209: GerritStatusPush should be able to ignore build results ------------------------+-------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: gerrit | ------------------------+-------------------- Changes (by tom.prince): * priority: major => minor * milestone: undecided => 0.8.6 Comment: This patch looks good. Should the default callback also ignore retry errors? Also, I'd like to properly attribute this patch (easiest way would be to simply submit a pullrequest on github. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 17 11:02:56 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 11:02:56 -0000 Subject: [Buildbot-commits] [Buildbot] #2209: GerritStatusPush should be able to ignore build results In-Reply-To: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> References: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> Message-ID: <054.3285638177d80d8223ad5a4e3361564b@buildbot.net> #2209: GerritStatusPush should be able to ignore build results ------------------------+-------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: gerrit | ------------------------+-------------------- Comment (by sanxiyn): I changed the default callback to ignore RETRY and sent a pull request. http://trac.buildbot.net/ticket/2209 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Fri Feb 17 14:40:59 2012 From: noreply at github.com (GitHub) Date: Fri, 17 Feb 2012 06:40:59 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 32d701: status_gerrit: selectively sending reviews Message-ID: <4f3e66fbd83e4_5a603f97a7a852f48548b@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 32d701784150ee93d0ebc1d58c88ab0d2006660b https://github.com/buildbot/buildbot/commit/32d701784150ee93d0ebc1d58c88ab0d2006660b Author: Seo Sanghyeon Date: 2012-02-17 (Fri, 17 Feb 2012) Changed paths: M master/buildbot/status/status_gerrit.py M master/docs/manual/cfg-statustargets.rst Log Message: ----------- status_gerrit: selectively sending reviews Do not send reviews if reviewCB returns None for message. Commit: 2532e97aab1652787696b1718320d8ce92ba1a4c https://github.com/buildbot/buildbot/commit/2532e97aab1652787696b1718320d8ce92ba1a4c Author: Tom Prince Date: 2012-02-17 (Fri, 17 Feb 2012) Changed paths: M master/buildbot/status/status_gerrit.py M master/docs/manual/cfg-statustargets.rst Log Message: ----------- Merge pull request #325 from sanxiyn/master GerritStatusPush should be able to ignore build results Fixes #2209. Compare: https://github.com/buildbot/buildbot/compare/f0fc394...2532e97 From nobody at buildbot.net Fri Feb 17 14:41:07 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 17 Feb 2012 14:41:07 -0000 Subject: [Buildbot-commits] [Buildbot] #2209: GerritStatusPush should be able to ignore build results In-Reply-To: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> References: <039.88f72758126bfcbf122259229033d5e9@buildbot.net> Message-ID: <054.6a1fcaad98398a9318af2a637b7d21e9@buildbot.net> #2209: GerritStatusPush should be able to ignore build results ------------------------+--------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: closed Priority: minor | Milestone: 0.8.6 Version: 0.8.5 | Resolution: fixed Keywords: gerrit | ------------------------+--------------------- Changes (by Tom Prince): * status: new => closed * resolution: => fixed Comment: Merge pull request #325 from sanxiyn/master GerritStatusPush should be able to ignore build results Fixes #2209. Changeset: 2532e97aab1652787696b1718320d8ce92ba1a4c -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sat Feb 18 05:44:45 2012 From: noreply at github.com (GitHub) Date: Fri, 17 Feb 2012 21:44:45 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 0e4142: fix docs typo Message-ID: <4f3f3acdb80e4_2c223fa603249af8280ec@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 0e4142f78400f4fa9661f221f99638f96d6b6748 https://github.com/buildbot/buildbot/commit/0e4142f78400f4fa9661f221f99638f96d6b6748 Author: Dustin J. Mitchell Date: 2012-02-17 (Fri, 17 Feb 2012) Changed paths: M master/docs/developer/database.rst Log Message: ----------- fix docs typo Commit: 9e0ef1b40ee5084d030a38603ed1ba43e62f0006 https://github.com/buildbot/buildbot/commit/9e0ef1b40ee5084d030a38603ed1ba43e62f0006 Author: Dustin J. Mitchell Date: 2012-02-17 (Fri, 17 Feb 2012) Changed paths: M master/docs/developer/database.rst Log Message: ----------- note that the db schema is not an API Compare: https://github.com/buildbot/buildbot/compare/2532e97...9e0ef1b From nobody at buildbot.net Mon Feb 20 09:36:48 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 09:36:48 -0000 Subject: [Buildbot-commits] [Buildbot] #2210: GroupBuildStep Message-ID: <040.e9a0b2b5b76a925a4abac664d0f8646f@buildbot.net> #2210: GroupBuildStep ------------------------+----------------------- Reporter: diorcety | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: ------------------------+----------------------- Hi, I had a special project requirement i had need to group multiple steps (more readable timeline). Globally, it will be interesting to create a tree of step. I have quickly(and ugly) created a solution to my problem and i want to share it with you. Regards, -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 14:39:01 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 14:39:01 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision Message-ID: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> #2211: svn switch before updating to revision ----------------------+----------------------- Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: ----------------------+----------------------- Hi. I have the following setup for svn checkout: mode='full', method='copy'. Also, there's a configured SVNPoller. Situation: 1. commit to trunk(it will be revision 1); 1. buildbot fetches that and builds revision 1; 1. commit to branch(rev.2); 1. buildbot does 'svn update --revision 2' in the source tree, which is checked out 'trunk'. 1. buildbot tries to build 'branch', which is actually trunk @ revision 1, while svnversion tells that it's revision 2. One can check the fact by doing 'svn log' in the source tree: the log will contain data only about rev.1, but not 2. That's not correct. First of all it should switch to 'branch' and do update to revision only after switching branches. I'm pretty sure my SVNPoller is configured right and it reports correct revision number, branch, etc. So the bug is actually in *not switching the branch before doing update*. P.S. Although my buildbot version is 0.8.5, I've applied patch from #2194 for 'svn update --revision $NUM' to work. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 14:41:57 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 14:41:57 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.35dcb50ac6bfcb530abc706d2d435c1e@buildbot.net> #2211: svn switch before updating to revision ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Changes (by doh): * cc: rusyanov@? (added) Comment: svn, version 1.6.12 (r955767) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 14:46:49 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 14:46:49 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.db2eedf83871d8c9b7aeeb49142f838c@buildbot.net> #2211: svn switch before updating to revision ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by tom.prince): I'm gussing you have something like {{{ SVN(svnurl="..../svnrepo/trunk") }}} Since a svn repository is organized merely by convention, and that different repos follow different conventinos, if you want to support branches, you need to give buildbot some guidance on how it is organized. I don't use svn, but I think something like {{{ SVN(baseURL="..../svnrepo/") }}} will work, so long as buildbot detects branches like "branch/branchname" or "trunk". -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 14:51:13 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 14:51:13 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.c7cd9011a77d401d0197aaefa139ed89@buildbot.net> #2211: svn switch before updating to revision ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by doh): Replying to [comment:2 tom.prince]: > I'm gussing you have something like > {{{ > SVN(svnurl="..../svnrepo/trunk") > }}} > My configuration for the source co step: {{{ SVN(baseURL=http://localhost/svn/repo, defaultBranch='trunk', username=source_user, password=mypasswd['source'], mode='full', method='copy', alwaysUseLatest=False, timeout=3600, locks=[source_lock.access('exclusive')])) }}} -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 15:00:41 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 15:00:41 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.b1ac73ac36b8d9749fc94046359c5b5e@buildbot.net> #2211: svn switch before updating to revision ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by doh): Replying to [comment:3 doh]: > > > My configuration for the source co step: > And the repository is organized in the following way(hope that helps to understand): > > repo/trunk > > repo/tags > > repo/branches/branch1 > > repo/branches/branch2 > > repo/branches/branch3 > The core problem lies in the fact that buildbot tries to update to correct revision number and it succeeds in terms of SVN, but fails in terms of checked out working copy(it will contain older data, from the first ever checked out branch). With mode='full', and method='copy' actually buildbot will never ever do 'svn co' after it was done for the first time, it will always do 'svn update' which never switches branches, it only tries to update either to HEAD, or to rev number. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 15:03:29 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 15:03:29 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.7f81e1bbed70f57a1ebb623b10f0285a@buildbot.net> #2211: svn switch before updating to revision ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by tom.prince): Having looked at the code again, it seems that the master-side code never checks to make sure the current URL is the same as the one currently checked out. This is certainly a bug. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 15:05:06 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 15:05:06 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.dc664721a2ffb3409651072842bbd7f6@buildbot.net> #2211: svn switch before updating to revision ----------------------+------------------------ Reporter: doh | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: | ----------------------+------------------------ Comment (by doh): Replying to [comment:5 tom.prince]: > Having looked at the code again, it seems that the master-side code never checks to make sure the current URL is the same as the one currently checked out. > > This is certainly a bug. Thank you for figuring that out :-) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:01:24 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:01:24 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command Message-ID: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> #2212: Property placeholder does not work in shell command ---------------------+---------------------------------- Reporter: DavidIAm | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: property, properties ---------------------+---------------------------------- This configuration fragment: {{{ tfactory = BuildFactory() tfactory.addStep(SVN( svnurl=url, mode='update' )) tfactory.addStep(ShellCommand(env={'BUILD_NUMBER': Property("buildnumber")}, command=["make",target])); }}} -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:03:17 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:03:17 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.89787a5e6326dee97c2e5badce33ff1d@buildbot.net> #2212: Property placeholder does not work in shell command ---------------------------------+------------------------ Reporter: DavidIAm | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: property, properties | ---------------------------------+------------------------ Comment (by DavidIAm): It appears that it is only allowing placeholders such as as a string containing ${buildnumber} through a regular expression (buildbot_slave-0.8.5-py2.7.egg/buildslave/runprocess.py:297)rather than allowing possible number value to be used as an environment value -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:03:58 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:03:58 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.7c0a1436bf41430a617f2e873ec3c07a@buildbot.net> #2212: Property placeholder does not work in shell command ---------------------------------+------------------------ Reporter: DavidIAm | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: property, properties | ---------------------------------+------------------------ Comment (by DavidIAm): Resulted in this traceback: {{{ remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last): File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/spread/pb.py", line 910, in _recvMessage netResult = object.remoteMessageReceived(self, message, netArgs, netKw) File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/spread/flavors.py", line 114, in remoteMessageReceived state = method(*args, **kw) File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/buildbot_slave-0.8.5-py2.7.egg/buildslave/bot.py", line 141, in remote_startCommand d = self.command.doStart() File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/buildbot_slave-0.8.5-py2.7.egg/buildslave/commands/base.py", line 145, in doStart d = defer.maybeDeferred(self.start) }}} -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:04:38 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:04:38 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.06c6af5aad0e1b7a92b5e0206eefac77@buildbot.net> #2212: Property placeholder does not work in shell command ---------------------------------+------------------------ Reporter: DavidIAm | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: property, properties | ---------------------------------+------------------------ Comment (by DavidIAm): --- --- File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/Twisted-11.1.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 134, in maybeDeferred result = f(*args, **kw) File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/buildbot_slave-0.8.5-py2.7.egg/buildslave/commands/shell.py", line 41, in start logEnviron=args.get('logEnviron', True), -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:04:58 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:04:58 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.0138713c8201a0952ece57732a58dad7@buildbot.net> #2212: Property placeholder does not work in shell command ---------------------------------+------------------------ Reporter: DavidIAm | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: property, properties | ---------------------------------+------------------------ Comment (by DavidIAm): File "/home/dihnen/tmp/buildbot/sandbox/local/lib/python2.7/site- packages/buildbot_slave-0.8.5-py2.7.egg/buildslave/runprocess.py", line 307, in __init__ newenv[key] = p.sub(subst, environ[key]) exceptions.TypeError: expected string or buffer exceptions.TypeError: expected string or buffer ] -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:20:47 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:20:47 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.ec6b85d9ba2b3eae9d30acb43d9cca4e@buildbot.net> #2212: Property placeholder does not work in shell command -----------------------+------------------------- Reporter: DavidIAm | Owner: tom.prince Type: defect | Status: accepted Priority: minor | Milestone: 0.8.+ Version: master | Resolution: Keywords: properties | -----------------------+------------------------- Changes (by tom.prince): * status: new => accepted * priority: major => minor * owner: => tom.prince * version: 0.8.5 => master * milestone: undecided => 0.8.+ * keywords: property, properties => properties Comment: What is going on here is that {{{Property("buildnumber")}}} gets rendered as an int, which then causes the environment substitution to fail later. Certainly we should have a better error message here, but I'm not sure if we want to be automatically coercing things to strings. Certainly it is reasonable for ints, but we don't also want to do it for arbitrary objects. A work around is to do {{{WithProperty("%(buildnumber)s")}}}, which does deliberately coerce things. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 20 17:24:50 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 20 Feb 2012 17:24:50 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.36e6bb5ef3e8680d3b30d0d08d446211@buildbot.net> #2212: Property placeholder does not work in shell command -----------------------+------------------------- Reporter: DavidIAm | Owner: tom.prince Type: defect | Status: accepted Priority: minor | Milestone: 0.8.+ Version: master | Resolution: Keywords: properties | -----------------------+------------------------- Comment (by DavidIAm): Update documentation at the very least to make it clear that Property doesn't change the type of the variable, and that environment variable values must be strings. Probably also be a goo d idea to annotate the data type of each of the common properties listed. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 15:18:00 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 15:18:00 -0000 Subject: [Buildbot-commits] [Buildbot] #2213: console webpage doesn't always show revisions when using branch=* Message-ID: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> #2213: console webpage doesn't always show revisions when using branch=* ----------------------+----------------------- Reporter: JocelynJ | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: web ----------------------+----------------------- Hi, I'm using a buildbot master that polls a SVN repository, with a busy trunk, and a quiet branch. I want to be able to use console.py?branch=branches/test so that only revisions and builds relevant to the branch are shown. What I can see is that, if there are too many revisions on trunk since last commit on the branch, the console doesn't show any revisions - which makes it hard to directly check if the branch is OK or not. According to the code in 0.8.5 of buildbot/status/web/console.py, this is because getAllChanges() only gets up to 25 revisions, and the filtering by branch is done a little later in stripRevisions(). I think these two functions should be merged, so that it is more similar to getRecentSourcestamps() in grid.py. Is the current behavior expected ? Is there any reason to split getAllChanges() and stripRevisions() in two different functions ? Thanks, Jocelyn -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Tue Feb 21 17:48:40 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 09:48:40 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 853b70: Merge branch 'source-urls' of git://github.com/tom... Message-ID: <4f43d8f8125b1_51131b69ae414866d@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 853b7036424e043ad5a9a474eb142348894ed18a https://github.com/buildbot/buildbot/commit/853b7036424e043ad5a9a474eb142348894ed18a Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/buildbot/steps/source/mercurial.py M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_mercurial.py M master/buildbot/test/unit/test_steps_source_svn.py M master/docs/manual/cfg-buildsteps.rst M master/docs/release-notes.rst Log Message: ----------- Merge branch 'source-urls' of git://github.com/tomprince/buildbot * 'source-urls' of git://github.com/tomprince/buildbot: Mercurial: Combine baseURL argument with repourl argument. SVN: Rename svnurl to repourl. (I fixed a typo in docs during the merge) From nobody at buildbot.net Tue Feb 21 17:52:15 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 17:52:15 -0000 Subject: [Buildbot-commits] [Buildbot] #1754: VC9 compile step assumes PlatformSDK is installed In-Reply-To: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> References: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> Message-ID: <056.9eb081ffae11789e3c4e61e476a595ee@buildbot.net> #1754: VC9 compile step assumes PlatformSDK is installed ----------------------+-------------------- Reporter: philippem | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: windows | ----------------------+-------------------- Changes (by dustin): * cc: callek (added) Comment: Callek, any suggestions here? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 18:02:25 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:02:25 -0000 Subject: [Buildbot-commits] [Buildbot] #1754: VC9 compile step assumes PlatformSDK is installed In-Reply-To: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> References: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> Message-ID: <056.688832fb0e7821b7be6e4b90798c1210@buildbot.net> #1754: VC9 compile step assumes PlatformSDK is installed ----------------------+-------------------- Reporter: philippem | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: windows | ----------------------+-------------------- Comment (by philippem): It is buildbot that is setting the paths, in buildbot\steps\vstudio.py in the VC9 build step. Depending on what version of MS visual studio is installed on the slave, and which optional SDKs, these paths may or may not exist. I had to do the above workaround (create empty dirs under c:\Program Files\...) to make the compile pass. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 18:03:52 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:03:52 -0000 Subject: [Buildbot-commits] [Buildbot] #2208: GerritChangeSource: orphan SSH process In-Reply-To: <039.e5839424d89858039e6fefe38987865c@buildbot.net> References: <039.e5839424d89858039e6fefe38987865c@buildbot.net> Message-ID: <054.9d636fc326f6493f890e55c52d836dc2@buildbot.net> #2208: GerritChangeSource: orphan SSH process --------------------+-------------------- Reporter: sanxiyn | Owner: Type: defect | Status: new Priority: minor | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: gerrit | --------------------+-------------------- Comment (by dustin): This: {{{ #!python def stopService(self): if self.process: self.process.signalProcess("KILL") }}} is killing the process, and then {{{ #!python def streamProcessStopped(self): self.process = None # if the service is stopped, don't try to restart if not self.parent: log.msg("service is not running; not reconnecting") return }}} is re-starting it. The check for `self.parent` is not the same as `self.running` which is, sadly, an undocumented attribute of service.Service. I think that the fix here is to add a new attribute to track whether the process should be running. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 18:06:30 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:06:30 -0000 Subject: [Buildbot-commits] [Buildbot] #1754: VC9 compile step assumes PlatformSDK is installed In-Reply-To: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> References: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> Message-ID: <056.2aebe2df400fc7042ca78bab1353dcd9@buildbot.net> #1754: VC9 compile step assumes PlatformSDK is installed ----------------------+-------------------- Reporter: philippem | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: windows | ----------------------+-------------------- Comment (by philippem): One possible fix is to determine a 'canonical' set of lib paths that should exist on a generic VS installed build slave, but there are multiple versions of the SDKs. Another fix is to create custom build steps derived from the provided VS build steps that work in the particular build slave environment. Maybe there is another way to determine the list of paths dynamically. My guess is that the path list in vstudio.py was created based on one particular VS-installed machine. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Tue Feb 21 18:07:01 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 10:07:01 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 097fed: Track the status of the gerritChangeSource process Message-ID: <4f43dd451d64_30f71bd5af01786c6@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 097fedf23a93cb6c67395eb4b0fd5a719889a2f4 https://github.com/buildbot/buildbot/commit/097fedf23a93cb6c67395eb4b0fd5a719889a2f4 Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/buildbot/changes/gerritchangesource.py Log Message: ----------- Track the status of the gerritChangeSource process separately from self.parent, which does not mean 'running' Fixes #2208. From nobody at buildbot.net Tue Feb 21 18:07:06 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:07:06 -0000 Subject: [Buildbot-commits] [Buildbot] #2208: GerritChangeSource: orphan SSH process In-Reply-To: <039.e5839424d89858039e6fefe38987865c@buildbot.net> References: <039.e5839424d89858039e6fefe38987865c@buildbot.net> Message-ID: <054.9dab342e6a86a49546bd2a21e7e89589@buildbot.net> #2208: GerritChangeSource: orphan SSH process --------------------+--------------------- Reporter: sanxiyn | Owner: Type: defect | Status: closed Priority: minor | Milestone: 0.8.+ Version: 0.8.5 | Resolution: fixed Keywords: gerrit | --------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Track the status of the gerritChangeSource process separately from self.parent, which does not mean 'running' Fixes #2208. Changeset: 097fedf23a93cb6c67395eb4b0fd5a719889a2f4 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 18:13:29 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:13:29 -0000 Subject: [Buildbot-commits] [Buildbot] #2210: GroupBuildStep In-Reply-To: <040.e9a0b2b5b76a925a4abac664d0f8646f@buildbot.net> References: <040.e9a0b2b5b76a925a4abac664d0f8646f@buildbot.net> Message-ID: <055.b16f5fe428df16fc8fa0d6f928a88904@buildbot.net> #2210: GroupBuildStep ------------------------+------------------------- Reporter: diorcety | Owner: Type: enhancement | Status: closed Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: worksforme Keywords: | ------------------------+------------------------- Changes (by dustin): * status: new => closed * resolution: => worksforme Comment: That is a clever implementation! Rather than do this while executing, I'd rather do this sort of filtering at the display stage -- that means that the data structures for storing what actually happened during a build stay simpler, and are not concerned with the structure of the display. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 18:17:12 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:17:12 -0000 Subject: [Buildbot-commits] [Buildbot] #1754: VC9 compile step assumes PlatformSDK is installed In-Reply-To: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> References: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> Message-ID: <056.af281f2a36da8af2e6d840f0df321ecc@buildbot.net> #1754: VC9 compile step assumes PlatformSDK is installed ----------------------+-------------------- Reporter: philippem | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: windows | ----------------------+-------------------- Comment (by dustin): In my opinion there are too many subclasses already. The best option is automatic detection (which should be as simple as some stat commands, right?), and failing that or if the autodetection doesn't work, allowing the paths to be specified as constructor arguments. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 18:26:06 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 18:26:06 -0000 Subject: [Buildbot-commits] [Buildbot] #2213: console webpage doesn't always show revisions when using branch=* In-Reply-To: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> References: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> Message-ID: <055.23838c0c88494f51d6f0dc3b3c9f81db@buildbot.net> #2213: console webpage doesn't always show revisions when using branch=* ----------------------+------------------------ Reporter: JocelynJ | Owner: Type: undecided | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: Keywords: web | ----------------------+------------------------ Comment (by dustin): All of these status-getting functions are a compromise between efficiency and getting the required data. On larger installs, fetching hundreds or thousands of changes on every page fetch can easily bring a master to its knees. If you can propose a change that will not appreciably diminish performance, I'm all ears. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 19:14:20 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 19:14:20 -0000 Subject: [Buildbot-commits] [Buildbot] #1754: VC9 compile step assumes PlatformSDK is installed In-Reply-To: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> References: <041.7922c18c8954db3a8c2932a71fd45dac@buildbot.net> Message-ID: <056.b94d90a1ecc546a3e99d34a9645c088e@buildbot.net> #1754: VC9 compile step assumes PlatformSDK is installed ----------------------+-------------------- Reporter: philippem | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.3 | Resolution: Keywords: windows | ----------------------+-------------------- Comment (by philippem): Automatic detection could work, but if multiple versions of SDKs are installed on the machine and the user wants a specific version, then there may be unexpected surprises. Maybe it's better to not put any default SDK paths, and let the user add the right paths in his or her own custom build step. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Tue Feb 21 20:37:53 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 12:37:53 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 6d4367: Change MailNotifier mode to allow for more flexibi... Message-ID: <4f4400a1ee1c9_20d43fed507e2afc215885@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 6d4367c807302f359eb9eb580c48233ef7e90fd9 https://github.com/buildbot/buildbot/commit/6d4367c807302f359eb9eb580c48233ef7e90fd9 Author: Federico G. Schwindt Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/buildbot/status/mail.py M master/buildbot/test/unit/test_status_mail.py M master/docs/manual/cfg-statustargets.rst Log Message: ----------- Change MailNotifier mode to allow for more flexibility The attached patch changes mode to be a list allowing for example to receive emails when there is a change and for any successive failures or only for warnings. The change also handles backward compatibility when passing a string and in particular for "all" and "warnings" string modes. The only change wrt to the current behaviour is that mode="all" will report whether the build failed, passed or warnings were found instead of "The Buildbot has finished a build" in the default message. I believe this is an improvement, ymmv. Commit: 6db569cea2bff8a6a891bd6c69730de5797cc18a https://github.com/buildbot/buildbot/commit/6db569cea2bff8a6a891bd6c69730de5797cc18a Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/docs/release-notes.rst Log Message: ----------- release notes for previous commit Compare: https://github.com/buildbot/buildbot/compare/097fedf...6db569c From nobody at buildbot.net Tue Feb 21 20:55:50 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 20:55:50 -0000 Subject: [Buildbot-commits] [Buildbot] #2205: Change MailNotifier mode to allow for more flexibility In-Reply-To: <037.42131bc1fd25aa098d8a6bccefb106af@buildbot.net> References: <037.42131bc1fd25aa098d8a6bccefb106af@buildbot.net> Message-ID: <052.25c2a49dd3f4d88d3f82179231632c55@buildbot.net> #2205: Change MailNotifier mode to allow for more flexibility ------------------------+------------------------ Reporter: fgsch | Owner: Type: enhancement | Status: closed Priority: minor | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: | ------------------------+------------------------ Changes (by dustin): * status: new => closed * resolution: => fixed Comment: Merged - thanks -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 20:56:30 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 20:56:30 -0000 Subject: [Buildbot-commits] [Buildbot] #2213: console webpage doesn't always show revisions when using branch=* In-Reply-To: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> References: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> Message-ID: <055.5b6e1c26fb139f4296ee3758ea659b6d@buildbot.net> #2213: console webpage doesn't always show revisions when using branch=* ---------------------+-------------------- Reporter: JocelynJ | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: web | ---------------------+-------------------- Changes (by dustin): * type: undecided => defect * milestone: undecided => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Tue Feb 21 21:19:30 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 13:19:30 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] a1c7b1: Only accept strings/lists for env values Message-ID: <4f440a6254cbc_69953f83414a7af02551f4@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: a1c7b124aead9d866fae881f5280266c0a085ef5 https://github.com/buildbot/buildbot/commit/a1c7b124aead9d866fae881f5280266c0a085ef5 Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/docs/manual/cfg-buildsteps.rst M slave/buildslave/runprocess.py M slave/buildslave/test/unit/test_runprocess.py Log Message: ----------- Only accept strings/lists for env values This includes a docs update as well as a better exception. Fixes #2212. From nobody at buildbot.net Tue Feb 21 21:19:39 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 21:19:39 -0000 Subject: [Buildbot-commits] [Buildbot] #2212: Property placeholder does not work in shell command In-Reply-To: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> References: <040.eb6a38407b6c42ca11af0cad5ff21a48@buildbot.net> Message-ID: <055.62cfd8b21cf2c956fb5ba90ed0e6011f@buildbot.net> #2212: Property placeholder does not work in shell command -----------------------+------------------------- Reporter: DavidIAm | Owner: tom.prince Type: defect | Status: closed Priority: minor | Milestone: 0.8.+ Version: master | Resolution: fixed Keywords: properties | -----------------------+------------------------- Changes (by Dustin J. Mitchell): * status: accepted => closed * resolution: => fixed Comment: Only accept strings/lists for env values This includes a docs update as well as a better exception. Fixes #2212. Changeset: a1c7b124aead9d866fae881f5280266c0a085ef5 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 21:25:58 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 21:25:58 -0000 Subject: [Buildbot-commits] [Buildbot] #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. In-Reply-To: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> References: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> Message-ID: <057.d3bc4c58201fd8ffcaaa4d754091a547@buildbot.net> #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. -----------------------+-------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: master | Resolution: Keywords: | -----------------------+-------------------- Comment (by dustin): What's the path to fixing this in 0.8.6? If that requires major work on the users support, I'd rather find a workaround for 0.8.6, or just leave it unfixed there (since this was the case in 0.8.5 as well). -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 21 21:28:34 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 21 Feb 2012 21:28:34 -0000 Subject: [Buildbot-commits] [Buildbot] #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. In-Reply-To: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> References: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> Message-ID: <057.6f9174dec665b343bbba3ba585906605@buildbot.net> #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. -----------------------+-------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: master | Resolution: Keywords: | -----------------------+-------------------- Comment (by tom.prince): The simple workaround is to not default to useUsers, since it is essentially broken with current state of the users code. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 01:53:41 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 01:53:41 -0000 Subject: [Buildbot-commits] [Buildbot] #2196: reconfig doesn't adopt new slaves In-Reply-To: <038.ec5a351e0b8b337cd2dcae9520bf017b@buildbot.net> References: <038.ec5a351e0b8b337cd2dcae9520bf017b@buildbot.net> Message-ID: <053.01ae02e11f2e33e69c345b39d68a1d22@buildbot.net> #2196: reconfig doesn't adopt new slaves -------------------+------------------------- Reporter: dustin | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: worksforme Keywords: | -------------------+------------------------- Changes (by dustin): * status: new => closed * resolution: => worksforme Comment: Hmm, I can't reproduce locally: {{{ 2012-02-21 17:57:33-0500 [-] beginning configuration update 2012-02-21 17:57:33-0500 [-] Loading configuration from '/Users/dustin/code/buildbot/t/buildbot/sand27/master/master.cfg' 2012-02-21 17:57:33-0500 [-] [] 2012-02-21 17:57:33-0500 [-] slaves [] 2012-02-21 17:57:33-0500 [-] (TCP Port 8010 Closed) 2012-02-21 17:57:33-0500 [-] Stopping factory 2012-02-21 17:57:33-0500 [-] RotateLogSite starting on 8010 2012-02-21 17:57:33-0500 [-] Starting factory 2012-02-21 17:57:33-0500 [-] Setting up http.log rotating 10 files of 10000000 bytes each 2012-02-21 17:57:33-0500 [-] WebStatus using (/Users/dustin/code/buildbot/t/buildbot/sand27/master/public_html) 2012-02-21 17:57:33-0500 [-] configuration update complete 2012-02-21 17:57:53-0500 [-] beginning configuration update 2012-02-21 17:57:53-0500 [-] Loading configuration from '/Users/dustin/code/buildbot/t/buildbot/sand27/master/master.cfg' 2012-02-21 17:57:53-0500 [-] [, ] 2012-02-21 17:57:53-0500 [-] slaves [, ] 2012-02-21 17:57:53-0500 [-] adding 1 new slaves, removing 0 2012-02-21 17:57:53-0500 [-] (TCP Port 8010 Closed) 2012-02-21 17:57:53-0500 [-] Stopping factory 2012-02-21 17:57:53-0500 [-] RotateLogSite starting on 8010 2012-02-21 17:57:53-0500 [-] Starting factory 2012-02-21 17:57:53-0500 [-] Setting up http.log rotating 10 files of 10000000 bytes each 2012-02-21 17:57:53-0500 [-] WebStatus using (/Users/dustin/code/buildbot/t/buildbot/sand27/master/public_html) 2012-02-21 17:57:53-0500 [-] configuration update complete 2012-02-21 17:58:16-0500 [Broker,0,127.0.0.1] slave 'example-slave' attaching from IPv4Address(TCP, '127.0.0.1', 56171) 2012-02-21 17:58:16-0500 [Broker,0,127.0.0.1] Starting buildslave keepalive timer for 'example-slave' 2012-02-21 17:58:16-0500 [Broker,0,127.0.0.1] Got slaveinfo from 'example- slave' 2012-02-21 17:58:16-0500 [Broker,0,127.0.0.1] bot attached }}} I suspect I missed something in this process, as I was working on merging the reconfig. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 01:54:12 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 01:54:12 -0000 Subject: [Buildbot-commits] [Buildbot] #2110: New SVN checkout step does not respect workdir when using full mode and copy method In-Reply-To: <042.2246a41c8b1a4e13b60fdad8042854d7@buildbot.net> References: <042.2246a41c8b1a4e13b60fdad8042854d7@buildbot.net> Message-ID: <057.55ac2933140e41a71c223e2a946f9bd2@buildbot.net> #2110: New SVN checkout step does not respect workdir when using full mode and copy method -----------------------+--------------------- Reporter: garmstrong | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: fixed Keywords: svn | -----------------------+--------------------- Changes (by dustin): * status: new => closed * resolution: => fixed Comment: This was fixed in the following commit: {{{ commit e82868da0232622fffee7b8408b51f4c0409850d Merge: 7fa49be f14ce7b Author: Dustin J. Mitchell Date: Thu Nov 17 23:23:11 2011 -0600 Merge branch 'svn_export' of git://github.com/in3xes/buildbot * 'svn_export' of git://github.com/in3xes/buildbot: Add export method to svn. Fixes #2078 Conflicts: master/buildbot/steps/source/svn.py Forward-ported (by dustin) and altered to not assume workdir='build', Release Notes added, docs edited. }}} -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Wed Feb 22 02:37:37 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 18:37:37 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 1e9a03: run 'svnversion' in source dir for full/export Message-ID: <4f4454f1d1af_7edf3fc5334d5afc14884@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 1e9a037de3dbc755e039f3e9883dfa9e980be2ea https://github.com/buildbot/buildbot/commit/1e9a037de3dbc755e039f3e9883dfa9e980be2ea Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- run 'svnversion' in source dir for full/export Fixes #2204. Commit: dd06fbd8c0d6500d6cfef3dc1a5d13842c9fc4bd https://github.com/buildbot/buildbot/commit/dd06fbd8c0d6500d6cfef3dc1a5d13842c9fc4bd Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- Merge remote-tracking branch 'lorentz/master' * lorentz/master: run 'svnversion' in source dir for full/export Compare: https://github.com/buildbot/buildbot/compare/a1c7b12...dd06fbd From nobody at buildbot.net Wed Feb 22 02:37:43 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 02:37:43 -0000 Subject: [Buildbot-commits] [Buildbot] #2204: svn export method and svnversion command In-Reply-To: <035.b638141107775d1746aa07461755ae4f@buildbot.net> References: <035.b638141107775d1746aa07461755ae4f@buildbot.net> Message-ID: <050.03617859a77dc960499f848d52a939e2@buildbot.net> #2204: svn export method and svnversion command -------------------+--------------------- Reporter: doh | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: fixed Keywords: | -------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: run 'svnversion' in source dir for full/export Fixes #2204. Changeset: 1e9a037de3dbc755e039f3e9883dfa9e980be2ea -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 02:48:34 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 02:48:34 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.71672c1489663a7fb570fb4d91d4ac6d@buildbot.net> #2211: svn switch before updating to revision -------------------+-------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | -------------------+-------------------- Changes (by dustin): * type: undecided => defect * milestone: undecided => 0.8.6 Comment: Tomprince and I discussed this briefly, and rather than try to re- implement the existing `.buildbot-sourcedata` functionality master-side, we should probably use native commands (in this case, `svn info`) to accomplish this check anyway. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 04:22:39 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 04:22:39 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.5d0483d9f2fc0fb6ccb548c9666d8a86@buildbot.net> #2211: svn switch before updating to revision -------------------+-------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | -------------------+-------------------- Comment (by dustin): Proposed fix is in https://github.com/buildbot/buildbot/pull/326 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 04:56:57 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 04:56:57 -0000 Subject: [Buildbot-commits] [Buildbot] #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. In-Reply-To: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> References: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> Message-ID: <057.37f87b23670d08d423be1633f276eaf3@buildbot.net> #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. -----------------------+-------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: master | Resolution: Keywords: | -----------------------+-------------------- Comment (by dustin): Looking back at v0.8.4, in that version if ``lookup`` wasn't set, nothing was sent. From what I can tell, in master, if ``lookup`` isn't set, then !MailNotifier will attempt to use the database, which most likely will not result in any email addresses, so no mail will be sent. In the rare case that the user support is actually set up, it *will* send email, though. So it sounds like this is no less functional than 0.8.4, and possibly more functional. Have I missed something? -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Wed Feb 22 05:16:22 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 21:16:22 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 915bb5: Document that user objects don't help MailNotifier... Message-ID: <4f447a26b27dd_7cf93f8fe5101af8182561@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 915bb5b1724b83e17e9f59c58a0477b6e33633f6 https://github.com/buildbot/buildbot/commit/915bb5b1724b83e17e9f59c58a0477b6e33633f6 Author: Dustin J. Mitchell Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/docs/manual/cfg-statustargets.rst Log Message: ----------- Document that user objects don't help MailNotifier .. yet This is actually the case in all previous versions of MailNotifier, although the documentation has been misleading/wrong since forever. Refs #2207. From nobody at buildbot.net Wed Feb 22 05:16:28 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 05:16:28 -0000 Subject: [Buildbot-commits] [Buildbot] #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. In-Reply-To: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> References: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> Message-ID: <057.6c6c30bdd8fa8be9a9c4c7d87d9ce1ba@buildbot.net> #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. -----------------------+-------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.6 Version: master | Resolution: Keywords: | -----------------------+-------------------- Comment (by Dustin J. Mitchell): Document that user objects don't help MailNotifier .. yet This is actually the case in all previous versions of MailNotifier, although the documentation has been misleading/wrong since forever. Refs #2207. Changeset: 915bb5b1724b83e17e9f59c58a0477b6e33633f6 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 05:20:32 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 05:20:32 -0000 Subject: [Buildbot-commits] [Buildbot] #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. In-Reply-To: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> References: <042.d785d3f7f38d095b49c36c4643c9ffd6@buildbot.net> Message-ID: <057.0805fb3273cfdd103b15f19de12d847d@buildbot.net> #2207: MailNotifier use the user-db by default, but that doesn't properly get populated. -----------------------+-------------------- Reporter: tom.prince | Owner: Type: defect | Status: new Priority: critical | Milestone: 0.8.+ Version: master | Resolution: Keywords: | -----------------------+-------------------- Changes (by dustin): * milestone: 0.8.6 => 0.8.+ Comment: To be fixed in a Future Version, then. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 06:25:55 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 06:25:55 -0000 Subject: [Buildbot-commits] [Buildbot] #2214: BuildStep's for multi-repo should include sourcebase in the names Message-ID: <042.390a8e63efa40f433cb326072e61e6cd@buildbot.net> #2214: BuildStep's for multi-repo should include sourcebase in the names ------------------------+----------------------- Reporter: jaredgrubb | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: ------------------------+----------------------- As per discussion for one of the multi-repo pull requests (starting here: https://github.com/buildbot/buildbot/pull/318#issuecomment-3983180) Basically, when adding in various source, build, test steps for multiple repositories, the names of the steps end up being ambigous. For example, you get things like "svn","svn_1", etc. Would be great if the Steps automatically mixed in a tag (probably the codebase?) into the name and/or the description(Done) fields. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 06:33:35 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 06:33:35 -0000 Subject: [Buildbot-commits] [Buildbot] #2215: GerritChangeSource should set repository attribute Message-ID: <039.2cb922b9b03fa684b78e31065236feaa@buildbot.net> #2215: GerritChangeSource should set repository attribute ------------------------+----------------------- Reporter: sanxiyn | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: gerrit ------------------------+----------------------- So that Git() build step can check out any Gerrit project. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Wed Feb 22 06:52:34 2012 From: noreply at github.com (GitHub) Date: Tue, 21 Feb 2012 22:52:34 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] faa669: GerritChangeSource should set repository attribute Message-ID: <4f4490b213ea4_7df93fea0b7752ec121779@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: faa6694e01c6921b72278dc0cfa497e71c482944 https://github.com/buildbot/buildbot/commit/faa6694e01c6921b72278dc0cfa497e71c482944 Author: Seo Sanghyeon Date: 2012-02-21 (Tue, 21 Feb 2012) Changed paths: M master/buildbot/changes/gerritchangesource.py M master/buildbot/test/unit/test_changes_gerritchangesource.py Log Message: ----------- GerritChangeSource should set repository attribute So that Git() build step can check out any Gerrit project. Fixes #2215. From nobody at buildbot.net Wed Feb 22 06:52:40 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 06:52:40 -0000 Subject: [Buildbot-commits] [Buildbot] #2215: GerritChangeSource should set repository attribute In-Reply-To: <039.2cb922b9b03fa684b78e31065236feaa@buildbot.net> References: <039.2cb922b9b03fa684b78e31065236feaa@buildbot.net> Message-ID: <054.133ed0deff78e8d5fe086ee9f0422927@buildbot.net> #2215: GerritChangeSource should set repository attribute ------------------------+------------------------ Reporter: sanxiyn | Owner: Type: enhancement | Status: closed Priority: major | Milestone: undecided Version: 0.8.5 | Resolution: fixed Keywords: gerrit | ------------------------+------------------------ Changes (by Seo Sanghyeon): * status: new => closed * resolution: => fixed Comment: GerritChangeSource should set repository attribute So that Git() build step can check out any Gerrit project. Fixes #2215. Changeset: faa6694e01c6921b72278dc0cfa497e71c482944 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 15:26:36 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 15:26:36 -0000 Subject: [Buildbot-commits] [Buildbot] #2214: BuildStep's for multi-repo should include sourcebase in the names In-Reply-To: <042.390a8e63efa40f433cb326072e61e6cd@buildbot.net> References: <042.390a8e63efa40f433cb326072e61e6cd@buildbot.net> Message-ID: <057.95a47461f44a1fc17b82f38bac185a88@buildbot.net> #2214: BuildStep's for multi-repo should include sourcebase in the names ------------------------+-------------------- Reporter: jaredgrubb | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: projrepo | ------------------------+-------------------- Changes (by dustin): * keywords: => projrepo * milestone: undecided => 0.8.+ Comment: Thanks for the bug! -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 22:36:09 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 22:36:09 -0000 Subject: [Buildbot-commits] [Buildbot] #2216: Would like a status page for slaves "one_line_per_slave" Message-ID: <042.7fc0add39447b632bf2ca8ba87feb18b@buildbot.net> #2216: Would like a status page for slaves "one_line_per_slave" ------------------------+----------------------- Reporter: lforschler | Owner: Type: enhancement | Status: new Priority: major | Milestone: undecided Version: 0.8.5 | Keywords: ------------------------+----------------------- Similar to the one_line_per_build status page, I would like a one_line_per_slave page. Reasoning: We have multiple slaves in each build group. Often times, one slave has a problem, so we end up with build results where we get several passing builds, then a failure, then passing again. It turns out, that one build slave often times goes awol. Having a one_line_per_slave page which shows the last 'N' build status (pass or fail) would make it easy to diagnose individual slaves which are having problems. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 22 22:46:36 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 22 Feb 2012 22:46:36 -0000 Subject: [Buildbot-commits] [Buildbot] #2216: Would like a status page for slaves "one_line_per_slave" In-Reply-To: <042.7fc0add39447b632bf2ca8ba87feb18b@buildbot.net> References: <042.7fc0add39447b632bf2ca8ba87feb18b@buildbot.net> Message-ID: <057.c739b536618d5b5a09e770af6981a97e@buildbot.net> #2216: Would like a status page for slaves "one_line_per_slave" ------------------------+-------------------- Reporter: lforschler | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.9.+ Version: 0.8.5 | Resolution: Keywords: web | ------------------------+-------------------- Changes (by tom.prince): * keywords: => web * priority: major => minor * milestone: undecided => 0.9.+ Comment: Is something like [http://buildbot.buildbot.net/buildslaves/xp-msysgit this] what you are after? I guess you probably want it broken out by builder? That would be reasonable, but probably needs to wait for the new JS UI (which is currently in the planning stages). In any case, patches would be welcome to implement this. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 00:19:07 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 00:19:07 -0000 Subject: [Buildbot-commits] [Buildbot] #2217: Allow MailNotifier's messageFormatter to be asynchronous Message-ID: <042.132b75752a27c925942736402dee281e@buildbot.net> #2217: Allow MailNotifier's messageFormatter to be asynchronous ------------------------+------------------- Reporter: tom.prince | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.+ Version: master | Keywords: mail ------------------------+------------------- [This](https://github.com/tomprince/commit/buildMessage-deferred) has code that does this, but it could use some tests to verify that it actually works asynchronously, and documentation. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 00:31:10 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 00:31:10 -0000 Subject: [Buildbot-commits] [Buildbot] #2217: Allow MailNotifier's messageFormatter to be asynchronous In-Reply-To: <042.132b75752a27c925942736402dee281e@buildbot.net> References: <042.132b75752a27c925942736402dee281e@buildbot.net> Message-ID: <057.d4d33187e572ed5ac65e88b1f85c6fd9@buildbot.net> #2217: Allow MailNotifier's messageFormatter to be asynchronous ------------------------+-------------------- Reporter: tom.prince | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.+ Version: master | Resolution: Keywords: mail | ------------------------+-------------------- Description changed by tom.prince: Old description: > [This](https://github.com/tomprince/commit/buildMessage-deferred) has > code that does this, but it could use some tests to verify that it > actually works asynchronously, and documentation. New description: [https://github.com/tomprince/buildbot/commit/buildMessage-deferred This] has code that does this, but it could use some tests to verify that it actually works asynchronously, and documentation. -- -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 04:35:48 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 04:35:48 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.d28f382020f7a4452fdaa62018ff050f@buildbot.net> #2211: svn switch before updating to revision -------------------+-------------------- Reporter: doh | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: Keywords: | -------------------+-------------------- Comment (by dustin): Some fixes (from pull 326) arrived in {{{ commit 20118110f428a8f630d693138c1ec6ecde6f33a2 Merge: 915bb5b fa49fe3 Author: Dustin J. Mitchell Date: Wed Feb 22 09:24:41 2012 -0600 Merge branch 'bug2211' * bug2211: typo mod_ -> mode_ use regular expressions to parse 'svn info' output Use 'svn info' to check source dirs' branches }}} with more to come. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Thu Feb 23 04:40:30 2012 From: noreply at github.com (GitHub) Date: Wed, 22 Feb 2012 20:40:30 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] fa49fe: typo mod_ -> mode_ Message-ID: <4f45c33ed939f_2de43ff045b51aec92147@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: fa49fe36f51692a2a99f6773990b21751f7de51c https://github.com/buildbot/buildbot/commit/fa49fe36f51692a2a99f6773990b21751f7de51c Author: Dustin J. Mitchell Date: 2012-02-22 (Wed, 22 Feb 2012) Changed paths: M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- typo mod_ -> mode_ Commit: 20118110f428a8f630d693138c1ec6ecde6f33a2 https://github.com/buildbot/buildbot/commit/20118110f428a8f630d693138c1ec6ecde6f33a2 Author: Dustin J. Mitchell Date: 2012-02-22 (Wed, 22 Feb 2012) Changed paths: M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- Merge branch 'bug2211' * bug2211: typo mod_ -> mode_ use regular expressions to parse 'svn info' output Use 'svn info' to check source dirs' branches Commit: bcbb713c1dc49bd56168f874b90460d611ea009f https://github.com/buildbot/buildbot/commit/bcbb713c1dc49bd56168f874b90460d611ea009f Author: Dustin J. Mitchell Date: 2012-02-22 (Wed, 22 Feb 2012) Changed paths: M master/buildbot/changes/gerritchangesource.py M master/buildbot/test/unit/test_changes_gerritchangesource.py Log Message: ----------- Merge branch 'master' of github.com:buildbot/buildbot * 'master' of github.com:buildbot/buildbot: GerritChangeSource should set repository attribute Commit: 8f131dae7a3d887ca5356f0bad37032c87a94162 https://github.com/buildbot/buildbot/commit/8f131dae7a3d887ca5356f0bad37032c87a94162 Author: Dustin J. Mitchell Date: 2012-02-22 (Wed, 22 Feb 2012) Changed paths: M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- remove bogus '@HEAD' from svn tests Commit: f39445ec76f6384a43116089f022abe13c66fcad https://github.com/buildbot/buildbot/commit/f39445ec76f6384a43116089f022abe13c66fcad Author: Dustin J. Mitchell Date: 2012-02-22 (Wed, 22 Feb 2012) Changed paths: M master/buildbot/steps/source/svn.py M master/buildbot/test/unit/test_steps_source_svn.py Log Message: ----------- Destroy the un-updatable directory when not updatable Without this, the subsequent 'svn checkout' will fail. Fixes #2211. Compare: https://github.com/buildbot/buildbot/compare/faa6694...f39445e From nobody at buildbot.net Thu Feb 23 04:40:43 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 04:40:43 -0000 Subject: [Buildbot-commits] [Buildbot] #2211: svn switch before updating to revision In-Reply-To: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> References: <035.0666053b1b23ea8e6ff0ae480daa61a0@buildbot.net> Message-ID: <050.80808aef93a3e43b33f0ad94b16d4bde@buildbot.net> #2211: svn switch before updating to revision -------------------+--------------------- Reporter: doh | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.5 | Resolution: fixed Keywords: | -------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Destroy the un-updatable directory when not updatable Without this, the subsequent 'svn checkout' will fail. Fixes #2211. Changeset: f39445ec76f6384a43116089f022abe13c66fcad -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 04:52:22 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 04:52:22 -0000 Subject: [Buildbot-commits] [Buildbot] #2114: database length restrictions on properties are silent In-Reply-To: <038.c9b81d79bc98f826f36732a2c508d9ef@buildbot.net> References: <038.c9b81d79bc98f826f36732a2c508d9ef@buildbot.net> Message-ID: <053.3d0d545762c558c25ed50bedadf220f3@buildbot.net> #2114: database length restrictions on properties are silent ---------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.4p2 | Resolution: Keywords: database | ---------------------+-------------------- Comment (by dustin): I need to figure out the function for MySQL's maximum number of characters given a text limit -- I don't think it's the identity function :( -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Thu Feb 23 15:09:30 2012 From: noreply at github.com (GitHub) Date: Thu, 23 Feb 2012 07:09:30 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] cc859c: Move Mock.__init__ call to the beginning of FakeRe... Message-ID: <4f4656aa37fbc_110c3ff63a644af4284f4@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: cc859c97d17b7e83dd896e5cb8aef5d78a0180ff https://github.com/buildbot/buildbot/commit/cc859c97d17b7e83dd896e5cb8aef5d78a0180ff Author: Tom Prince Date: 2012-02-23 (Thu, 23 Feb 2012) Changed paths: M master/buildbot/test/fake/web.py Log Message: ----------- Move Mock.__init__ call to the beginning of FakeRequest.__init__. Mock 0.8.0 breaks if it is called to late. From nobody at buildbot.net Thu Feb 23 16:19:55 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 16:19:55 -0000 Subject: [Buildbot-commits] [Buildbot] #2218: Add support for declarative configuration. Message-ID: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> #2218: Add support for declarative configuration. ------------------------+-------------------- Reporter: tom.prince | Owner: Type: enhancement | Status: new Priority: major | Milestone: 1.0.+ Version: 0.8.5 | Keywords: config ------------------------+-------------------- <@exarkun> That's why you also have plugins? <@exarkun> It's just about actually separating your code from your configuration <@exarkun> Your wacky auto-generated list of slave settings is fine, but put it in a module, unit test it (hey, document it! distribute it!) <@exarkun> and then in your _configuration_ say "and please use wacky auto-generate slave plugin" -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 16:23:17 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 16:23:17 -0000 Subject: [Buildbot-commits] [Buildbot] #2219: Make sample configuration modular. Message-ID: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> #2219: Make sample configuration modular. ------------------------+-------------------- Reporter: tom.prince | Owner: config Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Keywords: ------------------------+-------------------- Best practices for buildbot configuration are to have modular config of some sort. Don't ship with an example that doesn't follow best practices. <@exarkun> (Heck, the sample deployment _starts_ as a mess; to avoid a mess, you'd have to clean it up the config distributed with buildbot) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 16:57:58 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 16:57:58 -0000 Subject: [Buildbot-commits] [Buildbot] #2219: Make sample configuration modular. In-Reply-To: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> References: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> Message-ID: <057.a5837fdfd3d8804a12e0a1e06b6a4910@buildbot.net> #2219: Make sample configuration modular. ------------------------+--------------------- Reporter: tom.prince | Owner: config Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Resolution: Keywords: | ------------------------+--------------------- Comment (by dustin): Modular configs lead to difficulty with reloading, so they're not for the faint of heart. I'm not sure that the initial recommendation should look like that. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 16:58:24 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 16:58:24 -0000 Subject: [Buildbot-commits] [Buildbot] #2218: Add support for declarative configuration. In-Reply-To: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> References: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> Message-ID: <057.3c577e014d682adb4e76a8b4e7bb04cc@buildbot.net> #2218: Add support for declarative configuration. ------------------------+-------------------- Reporter: tom.prince | Owner: Type: enhancement | Status: new Priority: major | Milestone: 1.0.+ Version: 0.8.5 | Resolution: Keywords: config | ------------------------+-------------------- Comment (by dustin): What does this mean? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 16:59:26 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 16:59:26 -0000 Subject: [Buildbot-commits] [Buildbot] #2219: Make sample configuration modular. In-Reply-To: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> References: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> Message-ID: <057.7501a71842d5b5ed76f0f128e98d7203@buildbot.net> #2219: Make sample configuration modular. ------------------------+--------------------- Reporter: tom.prince | Owner: config Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Resolution: Keywords: | ------------------------+--------------------- Comment (by tom.prince): That won't be an issue, once we reconfig by graceful shutdown. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Thu Feb 23 17:01:55 2012 From: nobody at buildbot.net (Buildbot) Date: Thu, 23 Feb 2012 17:01:55 -0000 Subject: [Buildbot-commits] [Buildbot] #2219: Make sample configuration modular. In-Reply-To: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> References: <042.df4164f479ee7ff6c9f328d81c903457@buildbot.net> Message-ID: <057.6e700485f8db0da906f4a68078fa1db7@buildbot.net> #2219: Make sample configuration modular. ------------------------+--------------------- Reporter: tom.prince | Owner: config Type: enhancement | Status: new Priority: major | Milestone: 0.9.0 Version: 0.8.5 | Resolution: Keywords: | ------------------------+--------------------- Comment (by bdbaddog): I've got a pretty stable modular config which handles reconfig's well. The main trick was to get rid of : {{{ from XYZ import a,b,c }}} Since those aren't re-evaluated on reconfig. However doing something like: {{{ import XYZ a=XYZ.a b=XYZ.b c=XYZ.c }}} Seems to handle reconfig well. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 24 04:56:32 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 24 Feb 2012 04:56:32 -0000 Subject: [Buildbot-commits] [Buildbot] #2218: Add support for declarative configuration. In-Reply-To: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> References: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> Message-ID: <057.da81489b4b7b35ea1328b2e02fa59400@buildbot.net> #2218: Add support for declarative configuration. ------------------------+-------------------- Reporter: tom.prince | Owner: Type: enhancement | Status: new Priority: major | Milestone: 1.0.+ Version: 0.8.5 | Resolution: Keywords: config | ------------------------+-------------------- Comment (by sanxiyn): I guess this means configuring with data, instead of code, say JSON. I know you can do that already, but it would be nice to have built-in support if it can cover most cases, even if it does not cover all cases. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Fri Feb 24 15:29:45 2012 From: nobody at buildbot.net (Buildbot) Date: Fri, 24 Feb 2012 15:29:45 -0000 Subject: [Buildbot-commits] [Buildbot] #2213: console webpage doesn't always show revisions when using branch=* In-Reply-To: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> References: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> Message-ID: <055.ef6d3ea7cd655c2ddd63896e2518f317@buildbot.net> #2213: console webpage doesn't always show revisions when using branch=* ---------------------+-------------------- Reporter: JocelynJ | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: web | ---------------------+-------------------- Comment (by JocelynJ): I understand the issue: I handle an instance that has a lot of revisions, and the console interface can be slow sometime. I will see if I can efficiently merge these two functions. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 26 02:26:41 2012 From: noreply at github.com (GitHub) Date: Sat, 25 Feb 2012 18:26:41 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 503a9b: Document the deprecation of the old step factory i... Message-ID: <4f49986157da5_2d1e1108af0129e5@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 503a9bdb9a89ab718879464b07e4aeac7f3a3c00 https://github.com/buildbot/buildbot/commit/503a9bdb9a89ab718879464b07e4aeac7f3a3c00 Author: Tom Prince Date: 2012-02-24 (Fri, 24 Feb 2012) Changed paths: M master/buildbot/process/factory.py A master/buildbot/test/unit/test_process_factory.py M master/docs/release-notes.rst Log Message: ----------- Document the deprecation of the old step factory interface to BuildFactory. This has been deprecated for a long time. Warn people that we are removing it. The motivation for this is that we are changing how we are representing step factories, and don't want to expose that representation to the user. Commit: 9f590e9a9588b210b7880ba70481dcf512124f8b https://github.com/buildbot/buildbot/commit/9f590e9a9588b210b7880ba70481dcf512124f8b Author: Dustin J. Mitchell Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/process/factory.py A master/buildbot/test/unit/test_process_factory.py M master/docs/release-notes.rst Log Message: ----------- Merge pull request #328 from tomprince/deprecate-old-step-factories Document the deprecation of the old step factory interface to BuildFactory. Compare: https://github.com/buildbot/buildbot/compare/cc859c9...9f590e9 From noreply at github.com Sun Feb 26 02:44:15 2012 From: noreply at github.com (GitHub) Date: Sat, 25 Feb 2012 18:44:15 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] b44876: Don't use twisted.python.deprecate.warnAboutFuncti... Message-ID: <4f499c7f30eb1_222a1200ae89778e@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: b4487624e5eaefe8df17277c66f7b23015920226 https://github.com/buildbot/buildbot/commit/b4487624e5eaefe8df17277c66f7b23015920226 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/process/factory.py Log Message: ----------- Don't use twisted.python.deprecate.warnAboutFunction. This was introduced in twisted 11.0, so use warnings.warn, instead. From noreply at github.com Sun Feb 26 04:50:40 2012 From: noreply at github.com (GitHub) Date: Sat, 25 Feb 2012 20:50:40 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 2f8f6b: Collect all ConfigErrors, rather than raising an e... Message-ID: <4f49ba208a7e7_2d1e1108af0201ab@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 2f8f6b2ae173ad3d9322020c6568fea01c120384 https://github.com/buildbot/buildbot/commit/2f8f6b2ae173ad3d9322020c6568fea01c120384 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/buildslave.py M master/buildbot/config.py M master/buildbot/master.py M master/buildbot/process/buildstep.py M master/buildbot/schedulers/base.py M master/buildbot/schedulers/basic.py M master/buildbot/schedulers/dependent.py M master/buildbot/schedulers/timed.py M master/buildbot/status/mail.py M master/buildbot/status/web/baseweb.py M master/buildbot/steps/blocker.py M master/buildbot/steps/maxq.py M master/buildbot/steps/python.py M master/buildbot/steps/shell.py M master/buildbot/steps/transfer.py M master/buildbot/steps/trigger.py M master/buildbot/test/unit/test_config.py M master/buildbot/test/unit/test_master.py M master/docs/developer/config.rst M master/docs/release-notes.rst Log Message: ----------- Collect all ConfigErrors, rather than raising an exception at the first error. Instead of directly raising config.ConfigErrors, code should instead call config.error. In the case that this is called during config, the errors will be collected, and reported at the end. At any other point, an exception will be raised. Commit: f45655230f068d6b618ff7e3fe403afdc1ea3129 https://github.com/buildbot/buildbot/commit/f45655230f068d6b618ff7e3fe403afdc1ea3129 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/buildslave.py M master/buildbot/config.py M master/buildbot/master.py M master/buildbot/process/buildstep.py M master/buildbot/schedulers/base.py M master/buildbot/schedulers/basic.py M master/buildbot/schedulers/dependent.py M master/buildbot/schedulers/timed.py M master/buildbot/status/mail.py M master/buildbot/status/web/baseweb.py M master/buildbot/steps/blocker.py M master/buildbot/steps/maxq.py M master/buildbot/steps/python.py M master/buildbot/steps/shell.py M master/buildbot/steps/transfer.py M master/buildbot/steps/trigger.py M master/buildbot/test/unit/test_config.py M master/buildbot/test/unit/test_master.py M master/docs/developer/config.rst M master/docs/release-notes.rst Log Message: ----------- Merge branch 'log-all-config-errors' Compare: https://github.com/buildbot/buildbot/compare/b448762...f456552 From nobody at buildbot.net Sun Feb 26 04:58:26 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 26 Feb 2012 04:58:26 -0000 Subject: [Buildbot-commits] [Buildbot] #2114: database length restrictions on properties are silent In-Reply-To: <038.c9b81d79bc98f826f36732a2c508d9ef@buildbot.net> References: <038.c9b81d79bc98f826f36732a2c508d9ef@buildbot.net> Message-ID: <053.cb268685a3f0bf6c94bb446e8eda8d83@buildbot.net> #2114: database length restrictions on properties are silent ---------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.4p2 | Resolution: Keywords: database | ---------------------+-------------------- Comment (by dustin): Actually, in my test script, I do get a warning from msyql-python, but only the first time: /home/dustin/code/buildbot/t/buildbot/sand26/lib/python2.6/site- packages/sqlalchemy/engine/default.py:330: Warning: Data truncated for column 't' at row 1 On the bright side, MySQL's and Python's length functions seem to agree! -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 26 05:18:37 2012 From: noreply at github.com (GitHub) Date: Sat, 25 Feb 2012 21:18:37 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] c1573a: Fix sphinx formatting. Message-ID: <4f49c0ad7c983_394f176faec132f7@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: c1573a9e8310c8911fd14a54b9f5dc460cee7943 https://github.com/buildbot/buildbot/commit/c1573a9e8310c8911fd14a54b9f5dc460cee7943 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/docs/developer/config.rst Log Message: ----------- Fix sphinx formatting. Commit: c03fbc45f766c5ffe21f0a2e0e769c24cbc631b5 https://github.com/buildbot/buildbot/commit/c03fbc45f766c5ffe21f0a2e0e769c24cbc631b5 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/test/unit/test_process_factory.py Log Message: ----------- Don't try to test deprecation warnings on twisted < 8.2.0. twisted.trial.unittest.TestCase.flushWarnings was added in 8.2.0. Compare: https://github.com/buildbot/buildbot/compare/f456552...c03fbc4 From noreply at github.com Sun Feb 26 05:51:23 2012 From: noreply at github.com (GitHub) Date: Sat, 25 Feb 2012 21:51:23 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 3f61ab: Remove tests of deprecation warning. Message-ID: <4f49c85bb1ed8_66fd3fe09ec41af858755@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 3f61ab65b771666019d687b00dbe273115aef4f9 https://github.com/buildbot/buildbot/commit/3f61ab65b771666019d687b00dbe273115aef4f9 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/test/unit/test_process_factory.py Log Message: ----------- Remove tests of deprecation warning. The support for testing for warnings in old versions of twisted is somewhat broken. Rather than trying to get the tests working, just to scrap the code after release, don't test the warnings. Commit: abff29bcee9ed65f76dba24a86d4c296a1056733 https://github.com/buildbot/buildbot/commit/abff29bcee9ed65f76dba24a86d4c296a1056733 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/buildbot/config.py M master/buildbot/test/unit/test_config.py Log Message: ----------- Fix mistaken raising of ConfigError in MasterConfig.loadConfig. We test this by using a config that has embedded errors, as well as semantic errors that get added later. If an exception is raised prematurely, then the semantic errors wouldn't get reported. Compare: https://github.com/buildbot/buildbot/compare/c03fbc4...abff29b From noreply at github.com Sun Feb 26 06:06:03 2012 From: noreply at github.com (GitHub) Date: Sat, 25 Feb 2012 22:06:03 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] ad047f: Fix sphinx errors. Message-ID: <4f49cbcb8913_68223f9b7cc74af0934ef@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: ad047f0c6f3308fd49f5bbdca778e82b126e0424 https://github.com/buildbot/buildbot/commit/ad047f0c6f3308fd49f5bbdca778e82b126e0424 Author: Tom Prince Date: 2012-02-25 (Sat, 25 Feb 2012) Changed paths: M master/docs/developer/config.rst M master/docs/release-notes.rst Log Message: ----------- Fix sphinx errors. From noreply at github.com Sun Feb 26 14:41:31 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 06:41:31 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] bec8c6: Merge branch 'master' of github.com:buildbot/build... Message-ID: <4f4a449b1687_2d353fa15d6dfaf41679dc@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: bec8c6b0bb3f698b015e5af014bcecba0212229b https://github.com/buildbot/buildbot/commit/bec8c6b0bb3f698b015e5af014bcecba0212229b Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/config.py M master/buildbot/test/unit/test_config.py M master/buildbot/test/unit/test_process_factory.py M master/docs/developer/config.rst M master/docs/release-notes.rst Log Message: ----------- Merge branch 'master' of github.com:buildbot/buildbot * 'master' of github.com:buildbot/buildbot: Fix sphinx errors. Fix mistaken raising of ConfigError in MasterConfig.loadConfig. Remove tests of deprecation warning. From noreply at github.com Sun Feb 26 14:43:11 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 06:43:11 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] c7c173: Merge pull request #330 from jollyroger/fixperms Message-ID: <4f4a44ff22615_68543f9d314c9aec4675c@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: c7c173d555dc16d064c70a3e71e60396f00917ed https://github.com/buildbot/buildbot/commit/c7c173d555dc16d064c70a3e71e60396f00917ed Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: A master/buildbot/db/migrate/versions/__init__.py R master/buildbot/db/migrate/versions/__init__.py R master/docs/_images/header-text-transparent.png A master/docs/_images/header-text-transparent.png A master/docs/_static/buildbot.ico R master/docs/_static/buildbot.ico A media/header-text-transparent.png R media/header-text-transparent.png Log Message: ----------- Merge pull request #330 from jollyroger/fixperms Fix permissions for non-executable files From nobody at buildbot.net Sun Feb 26 14:49:06 2012 From: nobody at buildbot.net (Buildbot) Date: Sun, 26 Feb 2012 14:49:06 -0000 Subject: [Buildbot-commits] [Buildbot] #2114: database length restrictions on properties are silent In-Reply-To: <038.c9b81d79bc98f826f36732a2c508d9ef@buildbot.net> References: <038.c9b81d79bc98f826f36732a2c508d9ef@buildbot.net> Message-ID: <053.7140f0a1d87f7a9b8ef87bd061df7d56@buildbot.net> #2114: database length restrictions on properties are silent ---------------------+--------------------- Reporter: dustin | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.4p2 | Resolution: fixed Keywords: database | ---------------------+--------------------- Changes (by dustin): * status: new => closed * resolution: => fixed Comment: The trac hook failed, but this is fixed in {{{ commit 967b74ecaf1f0bbae842534280b3e56e5d52c17f Author: Dustin J. Mitchell Date: Sat Feb 25 22:59:04 2012 -0600 check database column length on insert for MySQL SQLite ignores length and just stores all the bytes you give it. Postgres will kindly produce an error rather than silently truncating. So this support is only really useful for MySQL, and stubs itself out everywhere else. Fixes #2114. }}} -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Sun Feb 26 19:21:14 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 11:21:14 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] e7861e: Fix bogus moockCheckCall in change_hook tests. Message-ID: <4f4a862a2af1f_52643fed589b0afc81956@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: e7861e71a971e203f323acedcf1d336111689480 https://github.com/buildbot/buildbot/commit/e7861e71a971e203f323acedcf1d336111689480 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/test/unit/test_status_web_change_hook.py Log Message: ----------- Fix bogus moockCheckCall in change_hook tests. The method doesn't exists, and bogusly succeeds, since the object is a mock. Commit: 164d599ccc01745be70a7a905a8d243bb73d3814 https://github.com/buildbot/buildbot/commit/164d599ccc01745be70a7a905a8d243bb73d3814 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/status/web/change_hook.py M master/buildbot/test/unit/test_status_web_change_hook.py Log Message: ----------- Catch all errors during change_hook processing. We shouldn't let errors in change_hooks escape to the user. Commit: 80a482d46d0a3c7adc3e16ad98f4d511faf39387 https://github.com/buildbot/buildbot/commit/80a482d46d0a3c7adc3e16ad98f4d511faf39387 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/status/web/hooks/github.py M master/buildbot/status/web/hooks/googlecode.py M master/buildbot/test/unit/test_status_web_change_hooks_github.py Log Message: ----------- Don't worry about errors in github or goolecode change hook. The generic code catches and logs all errors, so don't bother also doing it in the specific change hook. Commit: 757e0e34e18d366e114fe6b73dc40ef922c831dc https://github.com/buildbot/buildbot/commit/757e0e34e18d366e114fe6b73dc40ef922c831dc Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/status/web/change_hook.py M master/buildbot/status/web/hooks/github.py M master/buildbot/status/web/hooks/googlecode.py M master/buildbot/test/unit/test_status_web_change_hook.py M master/buildbot/test/unit/test_status_web_change_hooks_github.py Log Message: ----------- Merge branch 'change-hook-tests' Compare: https://github.com/buildbot/buildbot/compare/c7c173d...757e0e3 From noreply at github.com Sun Feb 26 19:48:22 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 11:48:22 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 64aa62: Fix pyflakes. Message-ID: <4f4a8c868e459_42913fc4b7a49af0641d6@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 64aa62017307fb36cc68ff4df40cf1b019e5bd9e https://github.com/buildbot/buildbot/commit/64aa62017307fb36cc68ff4df40cf1b019e5bd9e Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/status/web/hooks/github.py M master/buildbot/status/web/hooks/googlecode.py Log Message: ----------- Fix pyflakes. Commit: 80a3d9888e6078b2a149097e4eb87d4165b7f83f https://github.com/buildbot/buildbot/commit/80a3d9888e6078b2a149097e4eb87d4165b7f83f Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/status/status_push.py M master/buildbot/status/web/hooks/github.py Log Message: ----------- Remove bogus uses of python's logging module. We use twisted.python.log, but there were a couple of places using logging instead. Commit: 7021022ad2666da419e26daf6497cc326c86d026 https://github.com/buildbot/buildbot/commit/7021022ad2666da419e26daf6497cc326c86d026 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/status/web/hooks/github.py M master/buildbot/test/unit/test_status_web_change_hooks_github.py Log Message: ----------- Add test for non-branch case of github hook. Compare: https://github.com/buildbot/buildbot/compare/757e0e3...7021022 From noreply at github.com Mon Feb 27 01:02:31 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 17:02:31 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 087867: be more careful parsing exception messages Message-ID: <4f4ad62757a1f_64543fba0d4d3af893292@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 087867c605206fbf991239f203084c9b4abcdbf2 https://github.com/buildbot/buildbot/commit/087867c605206fbf991239f203084c9b4abcdbf2 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/db/pool.py Log Message: ----------- be more careful parsing exception messages Commit: 5d722e92ff1ea20400f7fff593e272034befee3e https://github.com/buildbot/buildbot/commit/5d722e92ff1ea20400f7fff593e272034befee3e Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/test/integration/test_upgrade.py Log Message: ----------- allow any upgrade test script to use a real db Commit: 0a3c28399e4c74e0d34cc33d8df66c435b991a28 https://github.com/buildbot/buildbot/commit/0a3c28399e4c74e0d34cc33d8df66c435b991a28 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: A master/buildbot/db/migrate/versions/021_fix_postgres_sequences.py M master/buildbot/test/integration/test_upgrade.py M master/buildbot/test/unit/test_db_migrate_versions_011_add_buildrequest_claims.py A master/buildbot/test/unit/test_db_migrate_versions_021_fix_postgres_sequences.py Log Message: ----------- Set postgres sequence values to allow inserts This fixes #2119, where the explicit inserts done as Buildbot imports changes from pickles skip the call to nextval('changes_changeid_seq'), and thus leave that sequence value out of sync with the table contents. Compare: https://github.com/buildbot/buildbot/compare/7021022...0a3c283 From nobody at buildbot.net Mon Feb 27 01:02:37 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 01:02:37 -0000 Subject: [Buildbot-commits] [Buildbot] #2119: upgrade-master sets auto-increment counters for id fields incorrectly in postgresql In-Reply-To: <038.b0cda045808f9a229824b84613d32f05@buildbot.net> References: <038.b0cda045808f9a229824b84613d32f05@buildbot.net> Message-ID: <053.107860ffdcd74a53485aaa920dd5ab7a@buildbot.net> #2119: upgrade-master sets auto-increment counters for id fields incorrectly in postgresql ---------------------+--------------------- Reporter: szager | Owner: Type: defect | Status: closed Priority: major | Milestone: 0.8.6 Version: 0.8.4p1 | Resolution: fixed Keywords: database | ---------------------+--------------------- Changes (by Dustin J. Mitchell): * status: new => closed * resolution: => fixed Comment: Set postgres sequence values to allow inserts This fixes #2119, where the explicit inserts done as Buildbot imports changes from pickles skip the call to nextval('changes_changeid_seq'), and thus leave that sequence value out of sync with the table contents. Changeset: 0a3c28399e4c74e0d34cc33d8df66c435b991a28 -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 27 01:07:28 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 17:07:28 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 15c1ab: Merge branch 'hgbuildbotbranch' of git://github.co... Message-ID: <4f4ad75056c57_2d1e1108af0777ac@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 15c1ab85bb805519a937c9e3bb87166128cbb0e6 https://github.com/buildbot/buildbot/commit/15c1ab85bb805519a937c9e3bb87166128cbb0e6 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/changes/hgbuildbot.py M master/docs/manual/cfg-changesources.rst Log Message: ----------- Merge branch 'hgbuildbotbranch' of git://github.com/benallard/buildbot * 'hgbuildbotbranch' of git://github.com/benallard/buildbot: hgbuildbot: reports by default the 'inrepo' type of branch Commit: d13975034d0af2ae0b57352aa795f2a58bf217f0 https://github.com/buildbot/buildbot/commit/d13975034d0af2ae0b57352aa795f2a58bf217f0 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/docs/release-notes.rst Log Message: ----------- add release notes for hgbuildbot default change Commit: 2ba0f13e41fbbe5c802c2845f04f52456154eb83 https://github.com/buildbot/buildbot/commit/2ba0f13e41fbbe5c802c2845f04f52456154eb83 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/changes/hgbuildbot.py Log Message: ----------- fix pyflake Compare: https://github.com/buildbot/buildbot/compare/0a3c283...2ba0f13 From noreply at github.com Mon Feb 27 01:08:46 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 17:08:46 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 605ef1: remove debug prints Message-ID: <4f4ad79ecaf30_64543fba0d4d3af8944fe@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 605ef113fd53c318b63b919ef24f317df2ed85cc https://github.com/buildbot/buildbot/commit/605ef113fd53c318b63b919ef24f317df2ed85cc Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/test/unit/test_db_migrate_versions_021_fix_postgres_sequences.py Log Message: ----------- remove debug prints From nobody at buildbot.net Mon Feb 27 01:13:28 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 01:13:28 -0000 Subject: [Buildbot-commits] [Buildbot] #2218: Add support for declarative configuration. In-Reply-To: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> References: <042.6eb1d8f39addc6ad3d2fe89bf0002f85@buildbot.net> Message-ID: <057.f8439bff71b7a41d15852043157e404d@buildbot.net> #2218: Add support for declarative configuration. ------------------------+-------------------- Reporter: tom.prince | Owner: Type: enhancement | Status: new Priority: major | Milestone: 1.0.+ Version: 0.8.5 | Resolution: Keywords: config | ------------------------+-------------------- Comment (by dustin): The typical prescription for this is that we should ship with a simple, default configuration that parses such a declarative configuration. This shouldn't require any particular changes to Buildbot itself (other than in create-master): the "sample" master.cfg can parse the JSON (or whatever format is selected) and produce the resulting config. It might make more sense for master.cfg to call some parsing code embedded in Buildbot itself, e.g. {{{ from buildbot.config import fromjson BuildmasterConfig = fromjson.load("master_cfg.json") }}} I'm quite open to this idea. I think the most difficult part will not be the code, but the additional documentation -- suddenly every piece of configuration must be documented both the "easy" way and the "hard" (but more flexible) way. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 27 01:47:50 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 17:47:50 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] fdbf96: add version to release notes, and use 'git log' Message-ID: <4f4ae0c645178_68223f9b7cc74af015496f@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: fdbf960dc141f544fb3dd6affe05dc10b570b712 https://github.com/buildbot/buildbot/commit/fdbf960dc141f544fb3dd6affe05dc10b570b712 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/docs/release-notes.rst Log Message: ----------- add version to release notes, and use 'git log' The github 'compare' view isn't up to the challenge of an entire release diff.. From noreply at github.com Mon Feb 27 01:47:51 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 17:47:51 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] Message-ID: <4f4ae0c7aac08_3e551933af47839d@sh2.rs.github.com.mail> Branch: refs/heads/buildbot-0.8.6 Home: https://github.com/buildbot/buildbot From noreply at github.com Mon Feb 27 02:02:42 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 18:02:42 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] fdd76b: archive release notes Message-ID: <4f4ae442e102b_2d353fa15d6dfaf421086@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: fdd76b9b7ead5664b1d93106c05d96fee4550cdb https://github.com/buildbot/buildbot/commit/fdd76b9b7ead5664b1d93106c05d96fee4550cdb Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/docs/release-notes.rst A master/docs/release-notes/0.8.6.rst Log Message: ----------- archive release notes Commit: c398ce8bf0389e5b02b6b6f540b8c64d71cfba93 https://github.com/buildbot/buildbot/commit/c398ce8bf0389e5b02b6b6f540b8c64d71cfba93 Author: Dustin J. Mitchell Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/docs/conf.py Log Message: ----------- ignore (intentionally) orphaned release notes Compare: https://github.com/buildbot/buildbot/compare/fdbf960...c398ce8 From noreply at github.com Mon Feb 27 02:02:45 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 18:02:45 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] Message-ID: <4f4ae44524044_42913fc4b7a49af089016@sh1.rs.github.com.mail> Branch: refs/tags/v0.8.7-pre Home: https://github.com/buildbot/buildbot From noreply at github.com Mon Feb 27 02:38:52 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 18:38:52 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 4a4719: Use with open() as f in tests. Message-ID: <4f4aecbc7b956_47ab1766af01085c4@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 4a471907000943dfdf118a05fa8ca3a63a484aaa https://github.com/buildbot/buildbot/commit/4a471907000943dfdf118a05fa8ca3a63a484aaa Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/test/integration/test_configs.py M master/buildbot/test/integration/test_upgrade.py M master/buildbot/test/unit/test_changes_mail.py M master/buildbot/test/unit/test_changes_svnpoller.py M master/buildbot/test/unit/test_config.py M master/buildbot/test/unit/test_schedulers_trysched.py M master/buildbot/test/unit/test_scripts_checkconfig.py M master/buildbot/test/unit/test_scripts_runner.py M master/buildbot/test/unit/test_status_logfile.py M master/buildbot/test/unit/test_steps_transfer.py M master/buildbot/test/unit/test_util_maildir.py M master/buildbot/test/util/change_import.py Log Message: ----------- Use with open() as f in tests. pypy uses a garbage collector, rather than reference counting, so we can't depend on file objects going out of scope to close them. Commit: 5315a57a7a4bbeb69d2c8f3ce978cde478f24294 https://github.com/buildbot/buildbot/commit/5315a57a7a4bbeb69d2c8f3ce978cde478f24294 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/__init__.py M master/buildbot/changes/changes.py M master/buildbot/changes/svnpoller.py M master/buildbot/clients/tryclient.py M master/buildbot/config.py M master/buildbot/db/migrate/versions/001_initial.py M master/buildbot/ec2buildslave.py M master/buildbot/manhole.py M master/buildbot/process/metrics.py M master/buildbot/scripts/reconfig.py M master/buildbot/scripts/runner.py M master/buildbot/status/build.py M master/buildbot/status/builder.py M master/buildbot/status/master.py M master/buildbot/status/persistent_queue.py M master/buildbot/status/status_push.py M master/buildbot/steps/package/rpm/rpmbuild.py M master/buildbot/steps/transfer.py Log Message: ----------- Use with open() as f in code. pypy uses a garbage collector, rather than reference counting, so we can't depend on file objects going out of scope to close them. Commit: 51354004361ae01a3f2631ddd158ca9826847508 https://github.com/buildbot/buildbot/commit/51354004361ae01a3f2631ddd158ca9826847508 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/test/unit/test_util_lru.py Log Message: ----------- Make LRUCache tests robust in the presence of a garbage collector. pypy uses a garbage collector, rather than reference counting, so we can't depend on object lifetimes matching binding lifetimes. Commit: dc817918a37669394c5a4a16f9fd638a1a4c759b https://github.com/buildbot/buildbot/commit/dc817918a37669394c5a4a16f9fd638a1a4c759b Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/__init__.py M master/buildbot/changes/changes.py M master/buildbot/changes/svnpoller.py M master/buildbot/clients/tryclient.py M master/buildbot/config.py M master/buildbot/db/migrate/versions/001_initial.py M master/buildbot/ec2buildslave.py M master/buildbot/manhole.py M master/buildbot/process/metrics.py M master/buildbot/scripts/reconfig.py M master/buildbot/scripts/runner.py M master/buildbot/status/build.py M master/buildbot/status/builder.py M master/buildbot/status/master.py M master/buildbot/status/persistent_queue.py M master/buildbot/status/status_push.py M master/buildbot/steps/package/rpm/rpmbuild.py M master/buildbot/steps/transfer.py M master/buildbot/test/integration/test_configs.py M master/buildbot/test/integration/test_upgrade.py M master/buildbot/test/unit/test_changes_mail.py M master/buildbot/test/unit/test_changes_svnpoller.py M master/buildbot/test/unit/test_config.py M master/buildbot/test/unit/test_schedulers_trysched.py M master/buildbot/test/unit/test_scripts_checkconfig.py M master/buildbot/test/unit/test_scripts_runner.py M master/buildbot/test/unit/test_status_logfile.py M master/buildbot/test/unit/test_steps_transfer.py M master/buildbot/test/unit/test_util_lru.py M master/buildbot/test/unit/test_util_maildir.py M master/buildbot/test/util/change_import.py Log Message: ----------- Merge branch 'pypy' Compare: https://github.com/buildbot/buildbot/compare/c398ce8...dc81791 From nobody at buildbot.net Mon Feb 27 02:50:59 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 02:50:59 -0000 Subject: [Buildbot-commits] [Buildbot] #2157: drop support for Python-2.4 In-Reply-To: <038.ef994c5ec15e437a654d0b735959adeb@buildbot.net> References: <038.ef994c5ec15e437a654d0b735959adeb@buildbot.net> Message-ID: <053.8a19117aac91be06e096fc0e88c01fbf@buildbot.net> #2157: drop support for Python-2.4 ------------------------+--------------------- Reporter: dustin | Owner: dustin Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: master | Resolution: Keywords: | ------------------------+--------------------- Comment (by dustin): Tests are disabled. -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 27 02:51:00 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 02:51:00 -0000 Subject: [Buildbot-commits] [Buildbot] #2182: deprecate compatibility with Twisted-8.x.x after 0.8.6 In-Reply-To: <038.223490c7b83417680ae2cbf57b74b762@buildbot.net> References: <038.223490c7b83417680ae2cbf57b74b762@buildbot.net> Message-ID: <053.19f18bc662dc671e2848963951f33503@buildbot.net> #2182: deprecate compatibility with Twisted-8.x.x after 0.8.6 ------------------------+-------------------- Reporter: dustin | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: | ------------------------+-------------------- Comment (by dustin): Tests are disabled. -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 27 02:53:33 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 18:53:33 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 377453: Don't use multiple bindings in a single with state... Message-ID: <4f4af02dd315a_68223f9b7cc74af01636db@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 377453d6bb2b388a6ee1fdafe54e92bb938d4311 https://github.com/buildbot/buildbot/commit/377453d6bb2b388a6ee1fdafe54e92bb938d4311 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/scripts/runner.py M master/buildbot/test/unit/test_steps_transfer.py Log Message: ----------- Don't use multiple bindings in a single with statement. This isn't supported on python 2.5 or 2.6. From noreply at github.com Mon Feb 27 03:14:31 2012 From: noreply at github.com (GitHub) Date: Sun, 26 Feb 2012 19:14:31 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 4c9b48: Also don't use with with tarfile. Message-ID: <4f4af517f0eb1_47ab1766af0111529@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 4c9b486a45c86522e53cd0c46806090f3efab987 https://github.com/buildbot/buildbot/commit/4c9b486a45c86522e53cd0c46806090f3efab987 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/test/integration/test_upgrade.py Log Message: ----------- Also don't use with with tarfile. It isn't supported by python 2.5. From nobody at buildbot.net Mon Feb 27 06:20:46 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 06:20:46 -0000 Subject: [Buildbot-commits] [Buildbot] #2123: Changes sent over the wire should be compressed In-Reply-To: <036.8cceb3fe6a6edabb86fbef518ee3826f@buildbot.net> References: <036.8cceb3fe6a6edabb86fbef518ee3826f@buildbot.net> Message-ID: <051.301f5ea40cf4c952ab84721a0d72aa66@buildbot.net> #2123: Changes sent over the wire should be compressed ------------------------+-------------------- Reporter: dank | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: | ------------------------+-------------------- Changes (by tom.prince): * milestone: 0.8.6 => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 27 06:20:55 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 06:20:55 -0000 Subject: [Buildbot-commits] [Buildbot] #2138: ability to plug-in new slave-side commands In-Reply-To: <038.1ae0499b220d892beff33bf2becdf64d@buildbot.net> References: <038.1ae0499b220d892beff33bf2becdf64d@buildbot.net> Message-ID: <053.328c483cf0620662d0b22e944ce00ca8@buildbot.net> #2138: ability to plug-in new slave-side commands ------------------------+--------------------- Reporter: dustin | Owner: dustin Type: enhancement | Status: new Priority: major | Milestone: 0.8.7 Version: 0.8.5 | Resolution: Keywords: | ------------------------+--------------------- Changes (by tom.prince): * milestone: 0.8.6 => 0.8.7 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Mon Feb 27 06:21:42 2012 From: nobody at buildbot.net (Buildbot) Date: Mon, 27 Feb 2012 06:21:42 -0000 Subject: [Buildbot-commits] [Buildbot] #2138: ability to plug-in new slave-side commands In-Reply-To: <038.1ae0499b220d892beff33bf2becdf64d@buildbot.net> References: <038.1ae0499b220d892beff33bf2becdf64d@buildbot.net> Message-ID: <053.16d4b6d6eeab380c4c57ec42d7bf9ab7@buildbot.net> #2138: ability to plug-in new slave-side commands ------------------------+--------------------- Reporter: dustin | Owner: dustin Type: enhancement | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: | ------------------------+--------------------- Changes (by tom.prince): * milestone: 0.8.7 => 0.8.+ -- Ticket URL: Buildbot Buildbot: build/test automation From noreply at github.com Mon Feb 27 18:16:17 2012 From: noreply at github.com (GitHub) Date: Mon, 27 Feb 2012 10:16:17 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 480144: Merge remote-tracking branch 'hborkhuis/multirepo2... Message-ID: <4f4bc871c404e_7661bd5af01838ee@sh2.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 480144e3fb73f8cbdaaa236c54019094c5c7facf https://github.com/buildbot/buildbot/commit/480144e3fb73f8cbdaaa236c54019094c5c7facf Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/changes/changes.py M master/buildbot/config.py M master/buildbot/db/changes.py A master/buildbot/db/migrate/versions/022_add_codebase.py M master/buildbot/db/model.py M master/buildbot/db/sourcestamps.py M master/buildbot/master.py M master/buildbot/process/build.py M master/buildbot/process/builder.py M master/buildbot/process/buildrequest.py M master/buildbot/process/properties.py M master/buildbot/schedulers/base.py M master/buildbot/schedulers/basic.py M master/buildbot/sourcestamp.py M master/buildbot/steps/source/oldsource.py M master/buildbot/test/fake/fakedb.py M master/buildbot/test/regressions/test_shell_command_properties.py M master/buildbot/test/unit/test_db_changes.py A master/buildbot/test/unit/test_db_migrate_versions_022_add_codebase.py M master/buildbot/test/unit/test_db_sourcestamps.py M master/buildbot/test/unit/test_master.py M master/buildbot/test/unit/test_process_build.py M master/buildbot/test/unit/test_process_builder.py M master/buildbot/test/unit/test_process_buildrequest.py M master/buildbot/test/unit/test_process_properties.py M master/buildbot/test/unit/test_schedulers_base.py M master/buildbot/test/unit/test_schedulers_dependent.py M master/buildbot/test/unit/test_schedulers_forcesched.py M master/buildbot/test/unit/test_schedulers_triggerable.py M master/buildbot/test/unit/test_schedulers_trysched.py M master/buildbot/test/unit/test_sourcestamp.py M master/docs/developer/config.rst M master/docs/manual/cfg-builders.rst M master/docs/manual/cfg-global.rst M master/docs/manual/cfg-properties.rst M master/docs/manual/concepts.rst M master/docs/release-notes.rst Log Message: ----------- Merge remote-tracking branch 'hborkhuis/multirepo2a' into multirepo Conflicts: master/docs/manual/concepts.rst master/docs/release-notes.rst master/buildbot/db/migrate/versions/022_add_codebase.py master/buildbot/test/unit/test_db_migrate_versions_022_add_codebase.py Commit: 27213414b20534e1f52e70df1908169b8c196d20 https://github.com/buildbot/buildbot/commit/27213414b20534e1f52e70df1908169b8c196d20 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/process/buildrequest.py Log Message: ----------- Don't compare lengths of changes when merging. Commit: f2c29d2377be64b51fcd66a30daea1568c198529 https://github.com/buildbot/buildbot/commit/f2c29d2377be64b51fcd66a30daea1568c198529 Author: Tom Prince Date: 2012-02-26 (Sun, 26 Feb 2012) Changed paths: M master/buildbot/process/builder.py M master/buildbot/process/buildrequest.py M master/buildbot/test/unit/test_process_buildrequest.py Log Message: ----------- Don't prohibit merging incompatible source stamps. We should check before trying to merge source stamp rather than while merging them. This way, if users give us a different function, merges will happen. Commit: 677b654ae9f03f1ca1e1a7f42c6893120a668eb7 https://github.com/buildbot/buildbot/commit/677b654ae9f03f1ca1e1a7f42c6893120a668eb7 Author: Harry Borkhuis Date: 2012-02-27 (Mon, 27 Feb 2012) Changed paths: M .mailmap M MAINTAINERS.txt M master/CREDITS M master/buildbot/__init__.py M master/buildbot/buildslave.py M master/buildbot/changes/changes.py M master/buildbot/changes/gerritchangesource.py M master/buildbot/changes/gitpoller.py M master/buildbot/changes/hgbuildbot.py M master/buildbot/changes/mail.py M master/buildbot/changes/svnpoller.py M master/buildbot/clients/tryclient.py M master/buildbot/config.py M master/buildbot/db/base.py M master/buildbot/db/buildsets.py M master/buildbot/db/changes.py M master/buildbot/db/migrate/versions/001_initial.py R master/buildbot/db/migrate/versions/021_add_codebase.py A master/buildbot/db/migrate/versions/021_fix_postgres_sequences.py A master/buildbot/db/migrate/versions/022_add_codebase.py R master/buildbot/db/migrate/versions/__init__.py A master/buildbot/db/migrate/versions/__init__.py M master/buildbot/db/pool.py M master/buildbot/db/sourcestamps.py M master/buildbot/db/state.py M master/buildbot/db/users.py M master/buildbot/ec2buildslave.py M master/buildbot/manhole.py M master/buildbot/master.py M master/buildbot/process/builder.py M master/buildbot/process/buildrequest.py M master/buildbot/process/buildstep.py M master/buildbot/process/factory.py M master/buildbot/process/metrics.py M master/buildbot/process/properties.py M master/buildbot/schedulers/base.py M master/buildbot/schedulers/basic.py M master/buildbot/schedulers/dependent.py M master/buildbot/schedulers/timed.py M master/buildbot/scripts/reconfig.py M master/buildbot/scripts/runner.py M master/buildbot/status/build.py M master/buildbot/status/builder.py M master/buildbot/status/mail.py M master/buildbot/status/master.py M master/buildbot/status/persistent_queue.py M master/buildbot/status/status_gerrit.py M master/buildbot/status/status_push.py M master/buildbot/status/web/baseweb.py M master/buildbot/status/web/change_hook.py M master/buildbot/status/web/hooks/base.py M master/buildbot/status/web/hooks/github.py M master/buildbot/status/web/hooks/googlecode.py M master/buildbot/steps/blocker.py M master/buildbot/steps/maxq.py M master/buildbot/steps/package/rpm/rpmbuild.py M master/buildbot/steps/python.py M master/buildbot/steps/shell.py M master/buildbot/steps/source/mercurial.py M master/buildbot/steps/source/svn.py M master/buildbot/steps/transfer.py M master/buildbot/steps/trigger.py M master/buildbot/test/fake/web.py M master/buildbot/test/integration/test_configs.py M master/buildbot/test/integration/test_upgrade.py M master/buildbot/test/unit/test_changes_gerritchangesource.py M master/buildbot/test/unit/test_changes_gitpoller.py M master/buildbot/test/unit/test_changes_mail.py M master/buildbot/test/unit/test_changes_mail_CVSMaildirSource.py M master/buildbot/test/unit/test_changes_svnpoller.py M master/buildbot/test/unit/test_config.py M master/buildbot/test/unit/test_db_base.py M master/buildbot/test/unit/test_db_migrate_versions_011_add_buildrequest_claims.py R master/buildbot/test/unit/test_db_migrate_versions_021_add_codebase.py A master/buildbot/test/unit/test_db_migrate_versions_021_fix_postgres_sequences.py A master/buildbot/test/unit/test_db_migrate_versions_022_add_codebase.py M master/buildbot/test/unit/test_master.py M master/buildbot/test/unit/test_process_buildrequest.py A master/buildbot/test/unit/test_process_factory.py M master/buildbot/test/unit/test_schedulers_trysched.py M master/buildbot/test/unit/test_scripts_checkconfig.py M master/buildbot/test/unit/test_scripts_runner.py M master/buildbot/test/unit/test_status_logfile.py M master/buildbot/test/unit/test_status_mail.py M master/buildbot/test/unit/test_status_web_base.py M master/buildbot/test/unit/test_status_web_change_hook.py M master/buildbot/test/unit/test_status_web_change_hooks_github.py M master/buildbot/test/unit/test_status_web_change_hooks_googlecode.py M master/buildbot/test/unit/test_steps_source_mercurial.py M master/buildbot/test/unit/test_steps_source_svn.py M master/buildbot/test/unit/test_steps_transfer.py M master/buildbot/test/unit/test_util_lru.py M master/buildbot/test/unit/test_util_maildir.py M master/buildbot/test/util/change_import.py M master/buildbot/test/util/querylog.py M master/contrib/bzr_buildbot.py M master/contrib/post_build_request.py A master/docs/_images/header-text-transparent.png R master/docs/_images/header-text-transparent.png A master/docs/_static/buildbot.ico R master/docs/_static/buildbot.ico M master/docs/conf.py M master/docs/developer/config.rst M master/docs/developer/database.rst M master/docs/developer/definitions.rst M master/docs/manual/cfg-buildsteps.rst M master/docs/manual/cfg-changesources.rst M master/docs/manual/cfg-statustargets.rst M master/docs/manual/concepts.rst M master/docs/manual/customization.rst M master/docs/release-notes.rst A master/docs/release-notes/0.8.6.rst R media/header-text-transparent.png A media/header-text-transparent.png M slave/buildslave/commands/darcs.py M slave/buildslave/runprocess.py M slave/buildslave/test/unit/test_commands_darcs.py M slave/buildslave/test/unit/test_runprocess.py Log Message: ----------- Merge pull request #3 from tomprince/multirepo Commit: 0cf668ea02789d2567438da67fdfbd7ec8ae19e5 https://github.com/buildbot/buildbot/commit/0cf668ea02789d2567438da67fdfbd7ec8ae19e5 Author: Harry Borkhuis Date: 2012-02-27 (Mon, 27 Feb 2012) Changed paths: M master/buildbot/sourcestamp.py Log Message: ----------- depickling of older sourcestamps including sourcestampsetid and codebase Commit: f8f7cad33ad4a408c45e2153d7ec15b1d3a4a50d https://github.com/buildbot/buildbot/commit/f8f7cad33ad4a408c45e2153d7ec15b1d3a4a50d Author: Harry Borkhuis Date: 2012-02-27 (Mon, 27 Feb 2012) Changed paths: M master/buildbot/test/integration/test_upgrade.py Log Message: ----------- test for upgrade to sourcestamp version 3 Compare: https://github.com/buildbot/buildbot/compare/4c9b486...f8f7cad From noreply at github.com Mon Feb 27 18:42:18 2012 From: noreply at github.com (GitHub) Date: Mon, 27 Feb 2012 10:42:18 -0800 Subject: [Buildbot-commits] [buildbot/buildbot] 665c2d: Fix pyflakes. Message-ID: <4f4bce8aed114_6e373f9a52e582fc66097@sh1.rs.github.com.mail> Branch: refs/heads/master Home: https://github.com/buildbot/buildbot Commit: 665c2d61c3fb6c3cb0625187931bc2ddf34ab1a4 https://github.com/buildbot/buildbot/commit/665c2d61c3fb6c3cb0625187931bc2ddf34ab1a4 Author: Tom Prince Date: 2012-02-27 (Mon, 27 Feb 2012) Changed paths: M master/buildbot/test/integration/test_upgrade.py Log Message: ----------- Fix pyflakes. From nobody at buildbot.net Tue Feb 28 09:22:16 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 28 Feb 2012 09:22:16 -0000 Subject: [Buildbot-commits] [Buildbot] #2213: console webpage doesn't always show revisions when using branch=* In-Reply-To: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> References: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> Message-ID: <055.b4b0feae0de8c4054ace429e43d823f0@buildbot.net> #2213: console webpage doesn't always show revisions when using branch=* ---------------------+-------------------- Reporter: JocelynJ | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: web | ---------------------+-------------------- Comment (by JocelynJ): I just did a quick trial, by moving the branch check to direct database queries. The patches are still rough, but do you agree with this solution ? -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Tue Feb 28 10:07:50 2012 From: nobody at buildbot.net (Buildbot) Date: Tue, 28 Feb 2012 10:07:50 -0000 Subject: [Buildbot-commits] [Buildbot] #2213: console webpage doesn't always show revisions when using branch=* In-Reply-To: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> References: <040.96d95683b9379f8676915d108b14c20b@buildbot.net> Message-ID: <055.355fb829511eb4262cf85d337ba51bc2@buildbot.net> #2213: console webpage doesn't always show revisions when using branch=* ---------------------+-------------------- Reporter: JocelynJ | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.+ Version: 0.8.5 | Resolution: Keywords: web | ---------------------+-------------------- Comment (by tom.prince): This looks like a reasonable approach. Thanks. If you are moving the filtering down to the db, why not move all the filtering there? Some tests will be needed for the db-connector changes. (Unfortunately, there are almost no tests for the web interface yet) -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 29 19:14:23 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 29 Feb 2012 19:14:23 -0000 Subject: [Buildbot-commits] [Buildbot] #2220: exception on upgrade-master Message-ID: <038.3515a64f56c22e16d2e95dd521a98b31@buildbot.net> #2220: exception on upgrade-master -------------------+----------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: undecided Version: 0.8.6 | Keywords: -------------------+----------------------- {{{ upgrading database (sqlite:///state.sqlite) Traceback (most recent call last): File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/internet/defer.py", line 391, in errback self._startRunCallbacks(fail) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/internet/defer.py", line 458, in _startRunCallbacks self._runCallbacks() File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/internet/defer.py", line 545, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/internet/defer.py", line 910, in gotResult _deferGenerator(g, deferred) --- --- File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/internet/defer.py", line 885, in _deferGenerator result = g.next() File "/home/deegan/dev/bb_git/buildbot/master/buildbot/scripts/runner.py", line 434, in upgradeMaster wfd.getResult() File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/internet/defer.py", line 864, in getResult self.result.raiseException() File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/python/threadpool.py", line 207, in _worker result = context.call(ctx, function, *args, **kwargs) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/python/context.py", line 118, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/twisted/python/context.py", line 81, in callWithContext return func(*args,**kw) File "/home/deegan/dev/bb_git/buildbot/master/buildbot/db/pool.py", line 177, in __thd rv = callable(arg, *args, **kwargs) File "/home/deegan/dev/bb_git/buildbot/master/buildbot/db/model.py", line 472, in thd upgrade(engine) File "/home/deegan/dev/bb_git/buildbot/master/buildbot/db/model.py", line 442, in upgrade schema.runchange(version, change, 1) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/migrate/versioning/schema.py", line 91, in runchange change.run(self.engine, step) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/migrate/versioning/script/py.py", line 145, in run script_func(engine) File "/home/deegan/dev/bb_git/buildbot/master/buildbot/db/migrate/versions/018_add_sourcestampset.py", line 45, in upgrade buildsets_table = sa.Table('buildsets', metadata, autoload=True) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/schema.py", line 303, in __new__ table._init(name, metadata, *args, **kw) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/schema.py", line 366, in _init self._autoload(metadata, autoload_with, include_columns) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/schema.py", line 390, in _autoload self, include_columns, exclude_columns File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/engine/base.py", line 2276, in run_callable return conn.run_callable(callable_, *args, **kwargs) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/engine/base.py", line 1900, in run_callable return callable_(self, *args, **kwargs) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/engine/default.py", line 259, in reflecttable return insp.reflecttable(table, include_columns, exclude_columns) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/engine/reflection.py", line 394, in reflecttable sql.text(col_d['default']), _reflected=True File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/sql/expression.py", line 1129, in text return _TextClause(text, bind=bind, *args, **kwargs) File "/home/deegan/dev/bb_git/sandbox/lib/python2.7/site- packages/sqlalchemy/sql/expression.py", line 2842, in __init__ self.text = self._bind_params_regex.sub(repl, text) exceptions.TypeError: expected string or buffer }}} -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 29 19:15:41 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 29 Feb 2012 19:15:41 -0000 Subject: [Buildbot-commits] [Buildbot] #2220: exception on upgrade-master In-Reply-To: <038.3515a64f56c22e16d2e95dd521a98b31@buildbot.net> References: <038.3515a64f56c22e16d2e95dd521a98b31@buildbot.net> Message-ID: <053.189b11d2032c5f12e674610b4b818330@buildbot.net> #2220: exception on upgrade-master -------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.6 | Resolution: Keywords: | -------------------+-------------------- Changes (by dustin): * milestone: undecided => 0.8.6 -- Ticket URL: Buildbot Buildbot: build/test automation From nobody at buildbot.net Wed Feb 29 23:52:46 2012 From: nobody at buildbot.net (Buildbot) Date: Wed, 29 Feb 2012 23:52:46 -0000 Subject: [Buildbot-commits] [Buildbot] #2220: exception on upgrade-master In-Reply-To: <038.3515a64f56c22e16d2e95dd521a98b31@buildbot.net> References: <038.3515a64f56c22e16d2e95dd521a98b31@buildbot.net> Message-ID: <053.677fc9f7f9ecee917b861864b8a9116d@buildbot.net> #2220: exception on upgrade-master -------------------+-------------------- Reporter: dustin | Owner: Type: defect | Status: new Priority: major | Milestone: 0.8.6 Version: 0.8.6 | Resolution: Keywords: | -------------------+-------------------- Comment (by tom.prince): {{{ 'pip freeze | grep sqlalchemy' in the venv, perhaps? sqlalchemy-migrate==0.7.1 SQLAlchemy==0.7.5 hmm buildbot ?version gets : Buildbot version: 0.8.5-500-gfdbf960 }}} -- Ticket URL: Buildbot Buildbot: build/test automation