Re: Issue 5564 in go: build: doc/articles/wiki check is flaky

[g...@googlecode.com]

Updates:
Summary: build: doc/articles/wiki check is flaky

Comment #2 on issue 5564 by r...@golang.org: build: doc/articles/wiki check
is flaky
http://code.google.com/p/go/issues/detail?id=5564#c2

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[g...@googlecode.com]

Updates:
Status: Accepted
Labels: -Priority-Triage Priority-Later Go1.2

Comment #1 on issue 5564 by r...@golang.org: build: doc/articles/wiki check
is flaky
http://code.google.com/p/go/issues/detail?id=5564#c1

[g...@googlecode.com]

Updates:
Owner: a...@golang.org
Labels: -Go1.2 Go1.2Maybe

Comment #3 on issue 5564 by r...@golang.org: build: doc/articles/wiki check is
flaky
http://code.google.com/p/go/issues/detail?id=5564#c3

This is a race. The shell script calls get -addr to get a free port, but by
the time the second run of get goes there, the port is busy. The scripting
is wrong. Something needs to hold that port open.

Demoting to Maybe, as this is not a release-blocker.

Assigning to adg.

[g...@googlecode.com]

Updates:
Labels: Testing

Comment #4 on issue 5564 by r...@golang.org: build: doc/articles/wiki check
is flaky
http://code.google.com/p/go/issues/detail?id=5564#c4

(No comment was entered for this change.)

[g...@googlecode.com]

Updates:
Labels: -Go1.2Maybe Go1.3

Comment #5 on issue 5564 by r...@golang.org: build: doc/articles/wiki check
is flaky
http://code.google.com/p/go/issues/detail?id=5564

[g...@googlecode.com]

Updates:
Status: Fixed

Comment #9 on issue 5564 by a...@golang.org: build: doc/articles/wiki check
is flaky
http://code.google.com/p/go/issues/detail?id=5564

This issue was closed by revision abda832be00f.