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

Issue 4517121: code review 4517121: runtime/proc_test: Fix spoiling of GOMAXPROCS. (Closed)

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

Description

runtime/proc_test: Fix spoiling of GOMAXPROCS. Fix the fact that the test leaves GOMAXPROCS=3 after itlsef and a running goroutine. I've added a benchmark to the file (not yet submitted) and it always runs with GOMAXPROCS=3 now.

Patch Set 1 #

Patch Set 2 : diff -r b0c691bce96b https://go.googlecode.com/hg/ #

Patch Set 3 : diff -r b0c691bce96b https://go.googlecode.com/hg/ #

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

Messages

Total messages: 3
dvyukov
Hello golang-dev@googlegroups.com (cc: dvyukov@google.com, golang-dev@googlegroups.com), I'd like you to review this change to https://go.googlecode.com/hg/
13 years, 11 months ago (2011-05-31 10:49:09 UTC) #1
rsc
LGTM
13 years, 11 months ago (2011-05-31 14:37:44 UTC) #2
rsc
13 years, 11 months ago (2011-05-31 14:38:53 UTC) #3
*** Submitted as http://code.google.com/p/go/source/detail?r=207b951b1430 ***

runtime: reset GOMAXPROCS during tests

Fix the fact that the test leaves GOMAXPROCS=3
and a running goroutine behind.

R=golang-dev, rsc
CC=dvyukov, golang-dev
http://codereview.appspot.com/4517121

Committer: Russ Cox <rsc@golang.org>
Sign in to reply to this message.

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