-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/go: go test -c
does not respect gcflags sometimes
#27681
Comments
This is a regression, it used to work in 1.10, and bisects to 2ce6da0 |
Change https://golang.org/cl/136275 mentions this issue: |
Just ran into this issue - any chance we could get a fix as a patch to 1.11? |
As far as I can see, this hasn't been fixed on tip yet. CC @bcmills @gopherbot please open a backport to 1.11 |
Backport issue(s) opened: #28346 (for 1.11). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
Thanks Ian! |
This is pretty bad for the debugging experience when it hits. Marking as a release blocker; feel free to undo it if I'm overstating things. |
I believe @jayconrod is looking in to this. |
I cannot tell from the Github issues what patch version of go1.11 the backport resolution of this issue is slated for. I would like to know when this will be/is fixed. |
@webern This is not yet fixed in any version of Go. It has to be fixed on tip first, then we can consider when it will be backported to 1.11. |
@jayconrod @aarzilli We are planning on cutting RC1 this week, do you think you can get the fix submitted between today and tomorrow? |
@FiloSottile We just need a small change in that CL, then it's ready to go. If the change isn't in by tomorrow morning, we can submit as-is, and I can submit a quick follow-up CL. |
So is the fix in |
@webern no, 1.12beta1 was cut two weeks ago and this fix was merged 3 hours ago. |
@webern This will be in RC1 which will cut soon. |
Change https://golang.org/cl/156377 mentions this issue: |
For bookkeeping, this is another CL that was related to this issue: https://golang.org/cl/156327 |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
All packages except
runtime
compiled with-N -l
What did you see instead?
It's pretty weird that it only gets applied to some packages.
The text was updated successfully, but these errors were encountered: