Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cmd/go: adjust test timeout using -timeout #2993

Closed
gopherbot opened this issue Feb 11, 2012 · 3 comments
Closed

cmd/go: adjust test timeout using -timeout #2993

gopherbot opened this issue Feb 11, 2012 · 3 comments
Labels
FrozenDueToAge
Milestone
Go1

Comments

@gopherbot
Copy link

by allard.guy.m:

What steps will reproduce the problem?

1.Run a test bed that will exceed 10 minutes total time.

What is the expected output?

The test bed runs for the required amount of time.

What do you see instead?

*** Test killed: ran too long.
FAIL    apackage    600.010s


Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

Ubuntu 11.10

Which revision are you using?  (hg identify)

go version weekly.2012-02-07 +52ba9506bd99


Please provide any additional information below.

Probably see line 543 in src/cmd/go/test.go

I originally thought that the -test.timeout value could be used to control this, but it
can not.
@robpike
Copy link
Contributor

robpike commented Feb 11, 2012

Comment 1:

As the comment says, some timeout is necessary to catch hung builders. A flag is
probably the answer, but not -test.timeout since (although it may not be obvious to the
user) that's for a different program.

Labels changed: added priority-go1, go1-must, removed priority-triage.

Owner changed to builder@golang.org.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Feb 12, 2012

Comment 2:

Owner changed to @rsc.

Status changed to Started.

@rsc
Copy link
Contributor

rsc commented Feb 13, 2012

Comment 3:

This issue was closed by revision d318ab2.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1
Development

No branches or pull requests
3 participants
@rsc @robpike @gopherbot