summaryrefslogtreecommitdiffstats
path: root/Tools/buildbot
Commit message (Collapse)AuthorAgeFilesLines
* Merge p3yk branch with the trunk up to revision 45595. This breaks a fairThomas Wouters2006-04-215-0/+83
| | | | | | | | | | | | | | | | | | | | number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
* Merge part of the trunk changes into the p3yk branch. This merges from 43030Thomas Wouters2006-04-211-1/+4
| | | | | | | | | | | | (branch-creation time) up to 43067. 43068 and 43069 contain a little swapping action between re.py and sre.py, and this mightily confuses svn merge, so later changes are going in separately. This merge should break no additional tests. The last-merged revision is going in a 'last_merge' property on '.' (the branch directory.) Arbitrarily chosen, really; if there's a BCP for this, I couldn't find it, but we can easily change it afterwards ;)
* Initialize VS environment in external.bat as well.Martin v. Löwis2006-03-131-0/+1
|
* Update to bsddb 4.4.20.Martin v. Löwis2006-03-131-0/+5
|
* Let the buildbot make a single pass in the test suite only.Martin v. Löwis2006-03-131-1/+1
|
* Update to bzip2 1.0.3Martin v. Löwis2006-03-132-0/+9
| | | | Make buildbot slaves automatically fetch bzip2 1.0.3.
* Adding the /useenv means that one's PATH actually gets through. This isTrent Mick2006-03-121-1/+1
| | | | | | | | important for the _ssl.vproj build. It calls build_ssl.py which tries to find a Perl to use. Without "/useenv" Visual Studio is getting a PATH from somewhere else (presumably from its internal environment configuration). The result is that build_ssl.py fallsback to its "well-known" locations for a Perl install.
* Move buildbot scripts to Tools/buildbot.Martin v. Löwis2006-03-123-0/+9