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

runtime: TestSelectStackAdjust "failed to trigger concurrent GC" #44610

Open
bcmills opened this issue Feb 25, 2021 · 4 comments
Open

runtime: TestSelectStackAdjust "failed to trigger concurrent GC" #44610

bcmills opened this issue Feb 25, 2021 · 4 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Feb 25, 2021

2021-02-25T04:55:35-666ad85/windows-amd64-2012

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
--- FAIL: TestSelectStackAdjust (0.02s)
    chan_test.go:780: failed to trigger concurrent GC
FAIL
FAIL	runtime	39.091s

This is the exact same failure mode as in #34693, which was believed to be fixed in December 2019. This is the first such failure in the logs since CL 210217, which suggests either a recent regression in the runtime (perhaps the GC pacer?) or a lingering very-low-probability flake in the test.

CC @mknyszek @aclements @ianlancetaylor

@bcmills
Copy link
Member Author

@bcmills bcmills commented Feb 25, 2021

Tentatively marking as release-blocker for Go 1.17 until we can determine whether this is actually a regression.

@bcmills bcmills added this to the Go1.17 milestone Feb 25, 2021
@aclements
Copy link
Member

@aclements aclements commented Mar 18, 2021

FYI, we had this failure a lot in toward the end of the 2019, starting with 2019-09-04T17:56:17-0607cdd and ending with 2019-12-05T22:08:26-e751af1, mostly on openbsd-arm though also on a smattering of other platforms. The one failure @bcmills linked is the only other time we've seen this.

@dmitshur
Copy link
Member

@dmitshur dmitshur commented Apr 8, 2021

There's a new occurrence today.

@aclements
Copy link
Member

@aclements aclements commented Apr 8, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants