What version of Go are you using (go version)?

$ go version
go version go1.14.2 darwin/amd64

Does this issue reproduce with the latest release?

I don't know. AFAIK, this is not a bug, so in theory, YES.

What operating system and processor architecture are you using (go env)?

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPRIVATE=""
GOTMPDIR=""
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/b4/t4v6zpln4rb16cvg747dz3j80000gn/T/go-build515811079=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I'm trying to benchmark a buffer library. I shall test write and read separately. But I need to write data to the buffer before read.

func BenchmarkXXX(b *testing.B) {
    buf := NewSomeBuffer()

    b.Run("Write", func (b *testing.B) {
        for i := 0; i < b.N; i++ {
            buf.Write(make([]byte, SOME_SIZE))
        }
    })

    b.Run("Write", func (b *testing.B) {
        for i := 0; i < b.N; i++ {
            buf.Write(make([]byte, SOME_SIZE))
        }

        b.ResetTimer() // Here is what went wrong

        for i := 0; i < b.N; i++ {
            buf.Read(make([]byte, SOME_SIZE))
        }
    })
}

What did you expect to see?

Hence in this scenario, read is much faster that write. It should ran similar amount of samples.

What did you see instead?

But, because b.ResetTimer undid all measurements. When go/benchmark trying to workout b.N values, It only measured the amount of time to read, It ended up timed out because of the enormous amount of data to write. Say 1,000,000 samples when test write alone, and 5,000,000 samples when test read