Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(657)

Issue 7319050: code review 7319050: runtime/debug: make TestFreeOSMemory repeatable (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years ago by dvyukov
Modified:
12 years ago
Reviewers:
rsc, albert.strasheim
CC:
golang-dev
Visibility:
Public.

Description

runtime/debug: make TestFreeOSMemory repeatable Fixes issue 4835.

Patch Set 1 #

Patch Set 2 : diff -r f30bdd45914c https://dvyukov%40google.com@code.google.com/p/go/ #

Patch Set 3 : diff -r f30bdd45914c https://dvyukov%40google.com@code.google.com/p/go/ #

Patch Set 4 : diff -r f30bdd45914c https://dvyukov%40google.com@code.google.com/p/go/ #

Patch Set 5 : diff -r f30bdd45914c https://dvyukov%40google.com@code.google.com/p/go/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -1 line) Patch
M src/pkg/runtime/debug/garbage_test.go View 1 1 chunk +2 lines, -1 line 0 comments Download

Messages

Total messages: 7
dvyukov
Hello golang-dev@googlegroups.com, I'd like you to review this change to https://dvyukov%40google.com@code.google.com/p/go/
12 years ago (2013-02-18 11:39:43 UTC) #1
albert.strasheim
LGTM. Fixes issue 4835.
12 years ago (2013-02-18 11:42:48 UTC) #2
dvyukov
On 2013/02/18 11:42:48, albert.strasheim wrote: > LGTM. > > Fixes issue 4835. Done.
12 years ago (2013-02-18 11:46:26 UTC) #3
dvyukov
*** Submitted as https://code.google.com/p/go/source/detail?r=bfaaa2075564 *** runtime/debug: make TestFreeOSMemory repeatable Fixes issue 4835. R=golang-dev, fullung CC=golang-dev ...
12 years ago (2013-02-18 11:46:55 UTC) #4
albert.strasheim
Hello I clearly didn't test this properly. It now fails with: --- FAIL: TestFreeOSMemory-89 (0.00 ...
12 years ago (2013-02-19 03:36:03 UTC) #5
rsc
It always works the first time, right? I suggest moving the allocation back to the ...
12 years ago (2013-02-19 16:32:52 UTC) #6
dvyukov
12 years ago (2013-02-20 08:15:56 UTC) #7
mailed https://codereview.appspot.com/7379043



On Tue, Feb 19, 2013 at 8:32 PM, <rsc@golang.org> wrote:

> It always works the first time, right? I suggest moving the allocation
> back to the global (it is there so that there cannot be any trace of the
> allocation lying around on the test goroutine stack) and then just make
> the test do:
>
> if big == nil {
>     return
> }
>
> so that subsequent tests do not repeat the test.
>
>
>
https://codereview.appspot.**com/7319050/<https://codereview.appspot.com/7319...
>
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b