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

cmd/cover: test timeout after 18m on plan9-arm #48416

Closed
millerresearch opened this issue Sep 16, 2021 · 5 comments
Closed

cmd/cover: test timeout after 18m on plan9-arm #48416

millerresearch opened this issue Sep 16, 2021 · 5 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@millerresearch
Copy link
Contributor

The cmd/cover test has been timing out quite frequently on plan9-arm. Most recent example here

I don't know how far back in time this goes. Is there a simple way to search failed test results to find the earliest occurrence?

@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Sep 16, 2021
@cagedmantis cagedmantis added this to the Backlog milestone Sep 16, 2021
@cagedmantis
Copy link
Contributor

You may be able to accomplish what you are seeking through the use of fetchlogs.

@millerresearch
Copy link
Contributor Author

You may be able to accomplish what you are seeking through the use of fetchlogs.

Thanks. Looks like the first failure was Jan 27 2021, then frequent occurrences from 3 March onwards.

I've managed to replicate the timeout once. Proximate cause is that go list -e json htmlunformatted appears to be deadlocked.

@millerresearch
Copy link
Contributor Author

The "deadlock" was lockedfile.openFile looping on a file in /tmp which was not actually locked: a bug in Plan 9 ramfs which was fixed some time ago, but somehow the patch wasn't applied on the plan9_arm builders. So, my fault. Should be OK now.

@millerresearch
Copy link
Contributor Author

Still getting timeouts, so I'd better reopen the issue and investigate further.

@millerresearch
Copy link
Contributor Author

There was a logic error in Plan 9 ramfs (used for /tmp on the builders), one consequence of which was a failure to maintain exclusive-open status on files. Now fixed, so it should be safe to close this issue.

@golang golang locked and limited conversation to collaborators Jul 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

3 participants