You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ 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.
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.
The text was updated successfully, but these errors were encountered: