| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test just doubled a certain number of times
and then gave up. On a mostly fast but occasionally
slow machine this may never make the test run
long enough to see the linear growth.
Change test to keep doubling until the first round
takes at least a full second, to reduce the effect of
occasional scheduling or other jitter.
The failure we saw had a time for the first round
of around 100ms.
Note that this test still passes once it sees a linear
effect, even with a very small total time.
The timeout here only applies to how long the execution
must be to support a reported failure.
LGTM=khr
R=khr
CC=golang-codereviews, rlh
https://codereview.appspot.com/164070043
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
iterdelete's run time varies; occasionally we get unlucky. To reduce spurious failures, average away some of the variation.
On my machine, 8 of 5000 runs (0.15%) failed before this CL. After this CL, there were no failures after 35,000 runs.
I confirmed that this adjusted test still fails before CL 141270043.
LGTM=khr
R=khr
CC=bradfitz, golang-codereviews
https://codereview.appspot.com/140610043
|
| |
|
|
|
|
|
| |
LGTM=bradfitz, iant
R=iant, bradfitz
CC=golang-codereviews
https://codereview.appspot.com/140510043
|
|
|
LGTM=rsc, khr
R=rsc, khr, bradfitz
CC=golang-codereviews
https://codereview.appspot.com/126720043
|
