Commit 1f9026c0 authored by Rob Pike's avatar Rob Pike

testing: don't print CPU count for tests, only benchmarks

The number of CPUs is of value when benchmarking but mostly
noise when testing. The recent change to default to the number
of CPUs available has made the tests noisier and confusing.

Fixes #11200

Change-Id: Ifc87d9ccb4177d73e304fb7ffcef4367bd163c9e
Reviewed-on: https://go-review.googlesource.com/11121Reviewed-by: 's avatarRuss Cox <rsc@golang.org>
parent 2c2770c3
......@@ -546,9 +546,6 @@ func RunTests(matchString func(pat, str string) (bool, error), tests []InternalT
continue
}
testName := tests[i].Name
if procs != 1 {
testName = fmt.Sprintf("%s-%d", tests[i].Name, procs)
}
t := &T{
common: common{
signal: make(chan interface{}),
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment