Heschi Kreinick 5e90bbcc6d testing: fix Benchmark() to start at 1 iteration, not 100 ... The run1 call removed in golang.org/cl/36990 was necessary to initialize the duration of the benchmark. With it gone, the math in launch() starts from 100. This doesn't work out well for second-long benchmark methods. Put it back. Updates #18815 Change-Id: I461f3466c805d0c61124a2974662f7ad45335794 Reviewed-on: https://go-review.googlesource.com/37530 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>		2017-03-01 11:06:34 +00:00
..
internal/testdeps	testing: print extra labels on benchmarks	2017-02-07 00:08:39 +00:00
iotest	…
quick	all: freeze net/rpc and reword the 'frozen' message in other frozen packages	2016-10-26 16:11:07 +00:00
allocs.go	…
allocs_test.go	…
benchmark.go	testing: fix Benchmark() to start at 1 iteration, not 100	2017-03-01 11:06:34 +00:00
benchmark_test.go	…
cover.go	…
example.go	cmd/go, testing: indicate when no tests are run	2016-10-19 02:34:44 +00:00
export_test.go	…
match.go	…
match_test.go	…
sub_test.go	testing: fix Benchmark() to start at 1 iteration, not 100	2017-03-01 11:06:34 +00:00
testing.go	testing: clarify T.Parallel() godoc wording	2017-02-07 15:30:49 +00:00
testing_test.go	Revert "testing: add T.Context method"	2016-12-09 04:04:11 +00:00