summaryrefslogtreecommitdiffstats
path: root/Tools/buildbot
Commit message (Collapse)AuthorAgeFilesLines
* Don't kill a normal instance of python running on windows when checkingNeal Norwitz2006-07-271-1/+12
| | | | | | to kill a cygwin instance. build\\python.exe was matching a normal windows instance. Prefix that with a \\ to ensure build is a directory and not PCbuild. As discussed on python-dev.
* Port cygwin kill_python changes from 2.4 branch.Martin v. Löwis2006-06-102-1/+8
|
* Use GetModuleFileNameEx instead of GetProcessImageFileName,Martin v. Löwis2006-04-172-3/+3
| | | | as the latter is not available on Windows 2000.
* Revert to 45478, disable kill_python command for now.Martin v. Löwis2006-04-174-11/+6
|
* Check whether disk space is full.Martin v. Löwis2006-04-171-0/+1
|
* Rename binary again; increase noise; stop trying to actually kill the process.Martin v. Löwis2006-04-174-3/+5
|
* Rename binaries again; increase noise.Martin v. Löwis2006-04-172-3/+3
|
* Rename binary to avoid conflicts with hanging processes on x86 w2k.Martin v. Löwis2006-04-172-2/+2
|
* Try some tracingMartin v. Löwis2006-04-171-2/+4
|
* Add kill_python command.Martin v. Löwis2006-04-174-0/+62
|
* The part checking for the sqlite DLL was looking at, andTim Peters2006-04-041-1/+1
| | | | | | | | | copying to, a wrong location (it copied the DLL under the Python directory, and gave it name 'PCbuild'). The Windows buildbots other than mine are probably hung now, waiting for someone to press "OK" on a popup box informing them that sqlite3.dll couldn't be found.
* sqlite on Windows:Tim Peters2006-04-041-1/+1
| | | | | | | | - The buildbot "fetch it" step failed at the end, due to using Unix syntax in the final "copy the DLL" step. test_sqlite was skipped as a result. - test_sqlite is no longer an expected skip on Windows.
* Add sqlite3 to the Windows build process.Martin v. Löwis2006-04-041-0/+4
|
* Update to Tk 8.4.12 and Tix 8.4.0Martin v. Löwis2006-03-211-0/+14
|
* Update to OpenSSL 0.9.8aMartin v. Löwis2006-03-211-0/+3
|
* Oops! Use python_d.exe _before_ it's destroyed :-)Tim Peters2006-03-161-1/+1
|
* Change the Windows buildbot "clean" step to removeTim Peters2006-03-161-1/+4
| | | | stale .pyc files.
* 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