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

os: TestReaddirnamesOneAtATime failed on windows-amd64-2016 #24742

Closed
alexbrainman opened this issue Apr 7, 2018 · 2 comments
Closed

os: TestReaddirnamesOneAtATime failed on windows-amd64-2016 #24742

alexbrainman opened this issue Apr 7, 2018 · 2 comments

Comments

@alexbrainman
Copy link
Member

@alexbrainman alexbrainman commented Apr 7, 2018

TestReaddirnamesOneAtATime failed on windows-amd64-2016 at 33eaf75

https://build.golang.org/log/03e86c1ca81554f89cb96158bceb0be6f2376f71

--- FAIL: TestReaddirnamesOneAtATime (0.04s)
	os_test.go:508: small read "PerfStringBackup.TMP" mismatch: pidgenx.dll
	os_test.go:508: small read "pidgenx.dll" mismatch: PING.EXE
	os_test.go:508: small read "PING.EXE" mismatch: PkgMgr.exe
	os_test.go:508: small read "PkgMgr.exe" mismatch: pku2u.dll
	os_test.go:508: small read "pku2u.dll" mismatch: pl-PL
	os_test.go:508: small read "pl-PL" mismatch: pla.dll
...
...
...
	os_test.go:508: small read "XpsPrint.dll" mismatch: zh-CN
	os_test.go:508: small read "zh-CN" mismatch: zh-HK
	os_test.go:508: small read "zh-HK" mismatch: zh-TW
FAIL
FAIL	os	2.772s

Alex

@mvdan mvdan added the OS-Windows label Apr 7, 2018
@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Apr 18, 2018

@ianlancetaylor ianlancetaylor added this to the Go1.11 milestone Apr 18, 2018
@alexbrainman

This comment has been minimized.

Copy link
Member Author

@alexbrainman alexbrainman commented Apr 18, 2018

Sorry @ianlancetaylor I did not have time to investigate issue on the day I reported it.

The TestReaddirnamesOneAtATime requires

// big directory that doesn't change often.

and we have chosen c:\windows\system32 as this is where Windows is installed. But looking at the failure message, it appears that some temp file was written into that directory in the middle of the test. I cannot think anything more suitable but c:\windows\system32 for this test - unless we want to create temp directory with many files specifically for that test.

This test is fairly old, but I do not remember seen this problem before. So I hope it will not happen soon enough to bother us again.

Closing this as unfortunate fake.

Alex

@golang golang locked and limited conversation to collaborators Apr 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.