[Morel Xavier]
> I currently have a (quite weak) computer that mostly sits idle (shares
> the web connection), Tbird 750; 640Mb RAM; Windows Server 2003 Standard
> Edition.
>
> Since the computer sits there doing nothing, I could probably put a
> buildbot on it if needed (since the python-dev thread states that many
> windows flavour would be appreciable and that Win2003 may not be
> extremely common), but i'd like to know how often it'll try to build,
> and how long the build itself may take on such a platform.
A problem for Windows buildbot slaves is that they need an appropriate
compiler. Does this machine have MS VC 7.1 installed? If not, it
can't compile the code. The Windows Python would also like to build
several other packages (like bz2 and Tcl/Tk).
An "update" style of slave does an svn update rather than a full
checkout, and that usually goes very fast after the first time.
Likewise compiling if binaries are left behind across runs.
For the rest, open a DOS box on this machine, cd to root of a Python
2.4.2 installation, and time
python Lib\test\regrtest.py -uall
That's about how long it will take on that machine to run all the
tests from the current trunk too. Really thorough tests take 8x as
long (with and without purging .pyc/.pyo files first, with and without
-O, and under release and debug builds: 2*2*2 = 8).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4