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
--- FAIL: TestNTNamespaceSymlink (5.38s)
path_windows_test.go:564: failed to run mklink C:\Data\Users\DefaultAccount\AppData\Local\Temp\TestNTNamespaceSymlink250384499\filelink \\?\Volume{ae420040-0000-0000-0000-800400000000}\\Data\Users\DefaultAccount\AppData\Local\Temp\TestNTNamespaceSymlink250384499\file: exit status 1 "You do not have sufficient privilege to perform this operation.\r\n"
FAIL
FAIL path/filepath 26.728s
I discovered that this test also fails on my Windows 10 computer.
The test passes on our windows-386 and windows-amd64 builders, probably, because the user that runs the test is allowed to create symlinks. But that is not always true.
So we need to adjust the test not to run, if user is not allowed to create symlinks.
While investigating recent windows-arm builder failure
https://build.golang.org/log/c00262fb40118e6917815b61ce7e1643b702bdc3
I discovered that this test also fails on my Windows 10 computer.
The test passes on our windows-386 and windows-amd64 builders, probably, because the user that runs the test is allowed to create symlinks. But that is not always true.
So we need to adjust the test not to run, if user is not allowed to create symlinks.
I will try and send a fix for this.
@jordanrh1 FYI
Alex
The text was updated successfully, but these errors were encountered: