Skip to content

Conversation

@compnerd
Copy link
Member

No description provided.

This introduces a new substitution for use in the CAS tests. The plain
variant of the target frontend invokes the tool with the variant target
triple and resource dir only. This allows us to properly invoke the
frontend for the CAS tests.
Enable the CAS test suite to execute on Windows.
Migrate two more instances of the lit test `RUN` lines to
`swift-build-modules` to ensure that all the modules are available for
the CAS build.
Adjust the test expectations to account for path separators on Windows.
The plugin server on Windows is an executable and thus has the `.exe`
extension that we did not match. Adjust the test for this naming
difference.
Ensure that we account for file system arc separators and extensions by
using the LLVM functions rather than trying to simply do string
matching. This allows us to properly handle the inputs on Windows.
Use `FileCheck` for the test validation instead of `diff`. This allows
us to match the different file system arc separator on Windows which is
different across the CAS, where everything is normalised, and the
uncached path where we get mixed paths.
@compnerd
Copy link
Member Author

@swift-ci please smoke test Windows platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant