The benchmarking part of the "testing" package supports stopping timers while
performing complex initialisation. Perhaps something analogous could be added for cpu
profiling, so that -cpuprofile can produce a data file that excludes samples for the
The current workaround is to avoid -cpuprofile in favour of calling
runtime.StartCPUProfile from within the benchmark.
The text was updated successfully, but these errors were encountered: