-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Switch To target-swiftc_driver #34284
Conversation
@swift-ci test |
Build failed |
Build failed |
Try to pass an explicit target to these tests so more exotic hosts do the right thing. rdar://70175753
Unfortunately, OutputFileMap does not normalize input names when it is constructing keys. Instead, keys to the map are formed by appending the entry's value directly onto the working directory with the test host's path separator convention. On Windows, the tests here were using UNIX-style path separators when passing inputs to the Driver, so the key was "C:\Path\To\File\A.swift" But the input path to the driver was "C:\Path\To\File/A.swift" To work around this - and to ultimately make the test slightly more portable - just use relative paths to the input files since we've already changed directories to the working directory before we run these driver commands.
0a1b3de
to
bcd0cb6
Compare
@swift-ci test |
Build failed |
@swift-ci test macOS |
@swift-ci test Windows |
Build failed |
@swift-ci test macOS |
Build failed |
@swift-ci test macOS |
⛵ |
Try to pass an explicit target to these tests so more exotic hosts do
the right thing.
rdar://70175753