The attached patch adds a --testonly mode to the 'perf.py' benchmark runner, which runs the selected benchmarks in the fastest possible way with just one interpreter (without filtering out slow benchmarks, or benchmarks that can't run in raw mode).

The intent is for this to be a relatively quick way to check that the benchmarks are not broken. I'm including the benchmarks in this mode in our continuous-build system (making sure the benchmarks will run when we need to do actual benchmarking), and this saves a significant amount of time while still allowing us to test all benchmarks (both --fast and --raw skip certain benchmarks).

Is this against https://github.com/python/performance or hg.python.org/benchmarks?

Please use the new benchmark suite: https://github.com/python/performance

performance already has such option: --debug-single-sample. It's already used by runtests.py which is run by tox and automatically by Travis CI. Enjoy!