"Go test -v" running for all tests's result(pass) is different form when I'm running individual test(fail)

[koseoyoung]

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

$ go version 
go1.15.2 darwin/amd64

Does this issue reproduce with the latest release?

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

go env Output

$ go env

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/seoyoungko/Library/Caches/go-build"
GOENV="/Users/seoyoungko/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/seoyoungko/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/seoyoungko/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.15.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/seoyoungko/go/src/github.com/iotexproject/iotex-core/go.mod"
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/5m/w57_zf0n76s7sy15dpnm9tx00000gn/T/go-build664261744=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

When I run all tests together by "go test -v" cmd, it pass for TestProtocol_ClaimReward test.
However, when I tried to run individual test by "go test -run TestProtocol_ClaimReward" cmd, it failed.

Is it possible to happen?

What did you expect to see?

Same result.

What did you see instead?

Different result

[mvdan]

Did you raise an issue on that project? It's entirely possible to write a test that fails when testing.Verbose is set, for example.

Also, if you still think this is a bug in Go, please provide clear steps to reproduce, including a git clone.

[gopherbot]

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)