[issue19501] Buildbot testing of 3.2 broken

2014-03-31 Thread Zachary Ware
Zachary Ware added the comment: With the demise of the 3.2 buildbot configuration, closing this issue. -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue19501] Buildbot testing of 3.2 broken

2013-12-22 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Antoine, can you fix this on the buildmaster or need I apply the patch in the > 3.2 branch? I'd rather you apply the patch in the 3.2 branch. -- ___ Python tracker

[issue19501] Buildbot testing of 3.2 broken

2013-11-05 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue19501] Buildbot testing of 3.2 broken

2013-11-04 Thread Georg Brandl
Georg Brandl added the comment: I haven't looked at 3.2 buildbots since the last point release. There will be only security releases in the future, still it'd be nice to be able to test on different bots. Antoine, can you fix this on the buildmaster or need I apply the patch in the 3.2 branch

[issue19501] Buildbot testing of 3.2 broken

2013-11-04 Thread Zachary Ware
New submission from Zachary Ware: After the recent commits to 3.2, I noticed that the only non-red 3.2 buildbots are the Windows bots; all other 3.2 bots are failing on `make touch`, which doesn't exist in 3.2. The simplest fix seems to me to be to add a fake 'touch' target to the Makefile, b