go: os: TestNetworkSymbolicLink failure with `The network path was not found.`

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

$ go version
go version go1.21rc3 windows/amd64

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
set GO111MODULE=auto
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Administrator\AppData\Local\go-build
set GOENV=C:\Users\Administrator\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=E:\gofile\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=E:\gofile
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,https://proxy.golang.org,direct
set GOROOT=C:\Users\Administrator\.go\current
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Users\Administrator\.go\current\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.21rc3
set GCCGO=gccgo
set GOAMD64=v2
set AR=ar
set CC=clang
set CXX=clang++
set CGO_ENABLED=0
set GOMOD=
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=D:\TEMP\go-build1363264525=/tmp/go-build -gno-record-gcc-switches
GOROOT/bin/go version: go version go1.21rc3 windows/amd64
GOROOT/bin/go tool compile -V: compile version go1.21rc3
lldb --version: lldb version 16.0.5
gdb --version: GNU gdb (GDB for MinGW-W64 x86_64, built by Brecht Sanders) 13.2

What did you do?

go test os

What did you expect to see?

Test passed.

What did you see instead?

--- FAIL: TestNetworkSymbolicLink (0.08s)
    os_windows_test.go:492: CreateFile \\localhost\GoSymbolicLinkTestShare\: The network path was not found.
FAIL
exit status 1
FAIL    os      6.903s

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 24 (22 by maintainers)

Commits related to this issue

Most upvoted comments

On my computer, execute Disable WindowsOptionalFeature Online FeatureName SMB1Protocol to turn off SMB and the test will fail. Execute Enable WindowsOptionalFeature Online FeatureName SMB1Protocol to turn on SMB and the test will succeed.

I’m not putting that in doubt. What I meant is that there should be another Windows capability or configuration that is missing in your computer that makes the test fail when SMB1Protocol is disabled, as I can pass the test with SMB1Protocol disabled. Therefore, if we skip the test when SMB1Protocol is disabled, we will be missing coverage from valid environments, like mine.

After enabling SMB, the test passed, and I sent CL 512736 to fix the failure when SMB was not enabled.