Nothing seems to happen for ~30s before the benchmarks start running. The issue appears to be that runTests runs its count loop 10000000 times, even though there are no tests to run.
One quick fix may be for runTests to exit immediately if len(tests) == 0, though I've distilled this issue down from my initial problem of a long time waiting for benchmarks to start in a package that has tests which I skip with -run=none. It would be nice to fix that case too. For that, perhaps the first pass through runTests records if it ran any tests. If not, the next iteration immediately breaks.
The text was updated successfully, but these errors were encountered: