benchmark timeout when benchtime set too long

[lkxiaolou]

When benchmark function execute time is very short, set benchtime=5s / 10s / 20s is ok.

BenchmarkNewObject-2            1000000000               0.279 ns/op

But set benchtime=120s will execute time out.

*** Test killed with quit: ran too long (11m0s).

1. benchtime short
   The B.n maybe 1 , 100 , 10000, 1000000, 100000000, 100000000 and exist.

2. benchtime long
   But set benchtime=120s, n = goalns * prevIters / prevns may be overflow(< 0) int64, and the B.n maybe 1, 100, 10000, 1000000, 100000000, 100000001, 100000002 .... and timeout.

[gopherbot]

This PR (HEAD: b535c98) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/369294 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

[gopherbot]

Message from Go Bot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://golang.org/doc/contribute.html#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://golang.org/s/release
for more details.

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/369294.
After addressing review feedback, remember to publish your drafts!