-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Disable TestFileManager.test_emptyFilename on Windows #5124
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
Conversation
@swift-ci please test |
Similar tests sometimes append a UUID string to make sure we're not conflicting with anything else, but this seems like a fine start. |
Looks like the Windows error is unrelated:
|
@swift-ci please test Windows Platform |
The fix for that error is now merged in |
@swift-ci please test Windows Platform |
This didn't fix the failure. I still haven't been able to reproduce locally, only in CI. I'll add some logging to this PR to debug. |
@swift-ci please test Windows Platform |
@swift-ci please test |
@swift-ci please test Windows Platform |
0f26415
to
1dd1008
Compare
I'm disabling the test to unblock Windows CI. I can reproduce readily in a swift-foundation PR to debug. |
@swift-ci please test |
@swift-ci please test Windows Platform |
1dd1008
to
867775f
Compare
@swift-ci please test |
@swift-ci please test Windows Platform |
1 similar comment
@swift-ci please test Windows Platform |
TestFileManager.test_emptyFilename
has been failing flakily on Windows with the following error:This test itself does not create
/tmp
or/tmp/t
, so it's suspected that another test might be creating one of these (or perhaps these files existed previously), changing the error thrown. This PR changes usage of/tmp/t
to a unique, non-existent file name/test_emptyFilename_nonExistent
instead.Update: That did not fix the issue, so we're disabling the test while we continue to investigate.