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: TestDebugCallUnsafePoint failures with <nil> instead of error on noopt builder since 2022-09-05 #55075

Closed
bcmills opened this issue Sep 14, 2022 · 2 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Sep 14, 2022
@bcmills
Copy link
Member Author

bcmills commented Sep 14, 2022

@golang/runtime, it looks like this may have been fixed around Sept. 7, but I can't find an obvious fix CL. Do we know for certain that this is fixed?

@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 14, 2022
@bcmills bcmills added this to the Go1.20 milestone Sep 14, 2022
@cuonglm
Copy link
Member

cuonglm commented Sep 14, 2022

I think this causes by https://go-review.googlesource.com/c/go/+/427135, the CL then be reverted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

3 participants