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

Jump to bottom

x/build: spurious "=C:=C:\golang" in environment #49882

Closed
bcmills opened this issue Nov 30, 2021 · 3 comments
Closed

x/build: spurious "=C:=C:\golang" in environment #49882

bcmills opened this issue Nov 30, 2021 · 3 comments
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows
Milestone
Unreleased

Comments

@bcmills
Copy link
Contributor

bcmills commented Nov 30, 2021

I noticed in https://storage.googleapis.com/go-build-log/18934e11/windows-amd64-2016_977b0eeb.log (a TryBot run on Windows) that the Windows builder environment includes a bogus entry that begins "=C:=C:\golang":

:: Running C:\workdir\go\bin\go with args […] and env ["GOBUILDEXIT=1" "=C:=C:\\golang" "ALLUSERSPROFILE=C:\\ProgramData" […]

This appears to be a very old bug: the earliest occurrence of it I can find dates to 2018:

2018-12-19T22:59:49-e147a91-f500f13/windows-amd64-2016

But even that may just be a reflection of the extent of my fetchlogs database rather than the extent of the bug.
@bcmills bcmills added OS-Windows Builders x/build issues (builders, bots, dashboards) labels Nov 30, 2021
@gopherbot gopherbot added this to the Unreleased milestone Nov 30, 2021
@mknyszek mknyszek added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Nov 30, 2021
@mknyszek
Copy link
Contributor

CC @dmitshur @cagedmantis

@gopherbot
Copy link

Change https://golang.org/cl/367896 mentions this issue: cmd/coordinator: join paths using the host's path separator

@bcmills bcmills mentioned this issue Nov 30, 2021
Open
@bcmills
Copy link
Contributor Author

bcmills commented Dec 9, 2021

According to https://devblogs.microsoft.com/oldnewthing/20100506-00/?p=14133, the =C: variable is produced by cmd.exe and is basically benign. (It looks weird in the logs, but shouldn't cause any harm.)

@bcmills bcmills closed this as completed Dec 9, 2021
@golang golang locked and limited conversation to collaborators Dec 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@mknyszek @bcmills @gopherbot