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

[SR-10819] Re-enable Foundation test TestFileManager.test_replacement #3327

Open
gottesmm opened this issue Jun 1, 2019 · 0 comments · May be fixed by #4656
Open

[SR-10819] Re-enable Foundation test TestFileManager.test_replacement #3327

gottesmm opened this issue Jun 1, 2019 · 0 comments · May be fixed by #4656
Assignees

Comments

@gottesmm
Copy link
Member

gottesmm commented Jun 1, 2019

Previous ID SR-10819
Radar None
Original Reporter @gottesmm
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Foundation
Labels Bug
Assignee @millenomi
Priority Medium

md5: 593e240b4c93068a7268ecb2e339221c

Issue Description:

It is failing on 18.04:

https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-18_04/5772/consoleFull

12:02:40 Test Case 'TestFileManager.test_replacement' started at 2019-05-31 19:01:44.920
12:02:40 note: Testing platform-specific replace implementation.
12:02:40 note: Testing with: a is directory? false, b is directory? false, using new metadata only? false, without deleting backup item? false
12:02:40 
<EXPR>:0: error: TestFileManager.test_replacement : threw error "Error Domain=NSCocoaErrorDomain Code=512 "(null)""
12:02:40 Test Case 'TestFileManager.test_replacement' failed (0.01 seconds)

I am disabling this so that we can get a toolchain this weekend hopefully.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
@Lukasa Lukasa linked a pull request Nov 18, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant