Comment 13 for bug 1290716

The ticket for python-scipy took 2hr 2min for me to complete with failed tests: http://paste.ubuntu.com/7086926/

Testrunner took 1 hr 4 min on a "standard.2xlarge" (30GB RAM | 8 VCPU | 30.0GB Disk) testbed instance and logging into the testbed during the test showed the tests themselves consuming 99+ % CPU.

On alderamin as Vincent points out this takes less time. This is definitely package specific and making a single selection for all the packages is overkill.

Leaving the testbed specification to be configurable by the user, probably via the cli appears to be the best solution for me, may be post phase-0.