cmd/go: 'go test -coverprofile' emits slash-separated paths on Windows #27486
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
OS-Windows
Milestone
Comments
bcmills
added
OS-Windows
NeedsInvestigation
|
@gopherbot, please backport to 1.11: this appears to be a regression from 1.9 or 1.10. |
|
Backport issue(s) opened: #27487 (for 1.11), #27488 (for 1.10). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
|
@rsc says that the paths are intentionally (now) supposed to be the import path + filename, since the file may be in the module cache rather than the local filesystem. Since @ramya-rao-a has updated the VSCode support to accept the new format and nobody else seems to have noticed, let's leave this as-is. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In microsoft/vscode-go#1847 (comment), @ramya-rao-a notes that in Go 1.11,
go test -coverprofileon Windows changed to emit slash-separated paths instead of using the OS-local separator.She has a workaround in
vscode(where the regression was detected), but there may be other tools currently broken on Windows.The text was updated successfully, but these errors were encountered: