From 1f9026c0bd489e96a04541d2f65ecfdc3bc53720 Mon Sep 17 00:00:00 2001 From: Rob Pike Date: Mon, 15 Jun 2015 10:59:00 -0700 Subject: [PATCH] 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/11121 Reviewed-by: Russ Cox --- src/testing/testing.go | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/testing/testing.go b/src/testing/testing.go index f64629fe53..fb22e3a559 100644 --- a/src/testing/testing.go +++ b/src/testing/testing.go @@ -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{}), -- 2.48.1