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.

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

gccgo tests: running a 'runoutput' test can hang the testsuite #6860

Open
mwhudson opened this issue Dec 1, 2013 · 2 comments

Comments

@mwhudson
Copy link
Contributor

commented Dec 1, 2013

I'm not sure if this is the right place to report this, but anyway:

Some of the gccgo tests are use a "runoutput" model where the test code is
compiled and run, generating more go code which is then run to be the 'real' test.  If
the code generating code hangs, though, the whole testsuite hangs -- the timeout that
protects the overall test suite execution from most hanging tests does not kick in.
@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 1:

Labels changed: added release-none, removed go1.3maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Dec 4, 2013

Comment 2:

Labels changed: added repo-gccgo.

@mwhudson mwhudson added new labels Dec 4, 2013

@bradfitz bradfitz removed the new label Dec 18, 2014

@rsc rsc added this to the Unplanned milestone Apr 10, 2015

@rsc rsc added Gccgo and removed release-none labels Apr 10, 2015

@rsc rsc modified the milestones: Gccgo, Unplanned Apr 15, 2015

@rsc rsc removed the Gccgo label Apr 15, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.