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

x/build/internal/task/releaselet: Windows installer fails to open device or file when installer file is located on ram disk #35251

Open
tamayika opened this issue Oct 30, 2019 · 3 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows
Milestone

Comments

@tamayika
Copy link

What version of Go are you using (go version)?

go1.13.3.windows-amd64.msi

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\owner\AppData\Local\go-build
set GOENV=C:\Users\owner\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\owner\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\owner\AppData\Local\Temp\go-build703477710=/tmp/go-build -gno-record-gcc-switches

What did you do?

  1. Download https://sourceforge.net/projects/imdisk-toolkit/, install, then create ram disk.
  2. Download windows golang installer and move it to ram disk root.
  3. Double click installer and try to install it by default setting.

What did you expect to see?

Installer installed files successfully.

What did you see instead?

Error dialog shows like attached images which means "cannot open the device or file specified" in japanese. Retry does not have any effect.
dev
If I moved installer to physical disk, installer works fine.
I've never experienced this problems in other installers.

@ALTree ALTree changed the title Windows golang installer fails to open device or file when installer file is located on ram disk x/build/cmd/release: Windows installer fails to open device or file when installer file is located on ram disk Oct 30, 2019
@gopherbot gopherbot added this to the Unreleased milestone Oct 30, 2019
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Oct 30, 2019
@ALTree ALTree added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed Builders x/build issues (builders, bots, dashboards) labels Oct 30, 2019
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Oct 30, 2019
@ALTree
Copy link
Member

ALTree commented Oct 30, 2019

cc @alexbrainman

Thanks for the report.

@tamayika Out of curiosity: is the inability to run the installer from a ramdisk a showstopper for you (and if yes, can you explain why, and what your use-case is)? Or does the obvious workaround - not running the installer from a ramdisk - work well for you, and this is more of an "exotic" defect report? I'm asking because the answer may help assessing the seriousness of this issue.

@tamayika
Copy link
Author

I usually use Firefox for browsing, and its download destination is ram disk. This is useful to cleanup unnecessary downloaded files when rebooting os.
I can't solved by googling this error message, so I doubted Firefox download bug and used Google Chrome instead. Google Chrome download destination is default(User Downloads dir), and it worked file. And I finally found the problem is installer location.
I don't think you must fix this bug because there is a workround, but I hope this issue will help someone who will meet this problem.

@alexbrainman
Copy link
Member

@tamayika I know very little about how Go installer works. I cannot help you.

Alex

@ALTree ALTree removed the Builders x/build issues (builders, bots, dashboards) label Dec 5, 2019
@dmitshur dmitshur changed the title x/build/cmd/release: Windows installer fails to open device or file when installer file is located on ram disk x/build/internal/task/releaselet: Windows installer fails to open device or file when installer file is located on ram disk Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows
Projects
None yet
Development

No branches or pull requests

4 participants