[pypy-issue] [issue1015] Add build to run the benchmarks with python 2.7 tip

Carsten Senger tracker at bugs.pypy.org
Wed Jan 25 14:45:48 CET 2012

Carsten Senger <senger at rehfisch.de> added the comment:

I went on and removed the guessing about what is the executable name, revision
and project from the interpreter path and turned that into explicit command line
arguments to runner.py. Then added the same options to upload the baseline
result and changed the build factories to use the new options.

I also added a dummy interpreter `nullpython.py` to circumvent running two real
benchmarks if we are only interested in the first and used it in the
CPythonBenchmark factory.

The --upload[-baseline]-urls parameter accepts comma seperated urls so we can
upload the results to both speed.pypy.org and speed.python.org (provided both
use the same 'project' and 'executable' names in codespeed).

PyPy bug tracker <tracker at bugs.pypy.org>

More information about the pypy-issue mailing list