cmd/go: 1.19beta1 fails to compile and run tests, breaking existing tests requiring invalid symbolic links

[thediveo]

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

$ go version
go version go1.19beta1 linux/arm64

Does this issue reproduce with the latest release?

This reproduces with the latest 1.19 beta1 beta release.

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

go env Output

$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/home/harald/.cache/go-build"
GOENV="/home/harald/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/.../go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/.../go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/.../sdk/go1.19beta1"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/.../sdk/go1.19beta1/pkg/tool/linux_arm64"
GOVCS=""
GOVERSION="go1.19beta1"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/.../workspaces/namespaces/lxkns/go.mod"
GOWORK="/home/.../workspaces/namespaces/go.work"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build644859308=/tmp/go-build -gno-record-gcc-switches"

What did you do?

$ git checkout https://github.com/thediveo/lxkns
$ cd lxkns
$ go1.19beta1 test -v ./species/
stat /home/harald/workspaces/namespaces/lxkns/discover/test/fdscan/proc/5678/fd/3: no such file or directory

What did you expect to see?

As with go 1.18.x the go cmd does not error and compiles and runs the tests as instructed. Any package test suite within the lxkns repository can be compiled and run without the go command aborting.

What did you see instead?

The go command aborting with the error message "stat /home/.../workspaces/namespaces/lxkns/discover/test/fdscan/proc/5678/fd/3: no such file or directory".

The go command does not build and run any test suite anywhere(!) within the lxkns module.

Background Information

In order to test correct error handling, some tests in the lxkns repository need to operate on deliberately broken symbolic links. Up to go 1.18 releases there were never any problems with invalid/broken symbolic links being present in the package tree, and especially any test data directories.

One such test example is the invalid symbolic link in discover/test/fdscan/proc/5678/fd/3.

[seankhliao]

please try tip, #53387 was closed a few days ago

[thediveo]

@seankhliao yes, the gotip go1.19-c847a2c fixed my issue for me too. Thank you very much for quickly spotting my issue and the "rescue", highly appreciated!