Skip to content

[Test] Fix the wrong subsitution of swift-frontend-target in tests #70530

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

cachemeifyoucan
Copy link
Contributor

There is no %swift-frontend-target subsitution in test, which is actually %target-swift-frontend. The wrong spelling is actually interpruted by lit as %swift-frontend-target, and surprising didn't break any tests as the last argument from subsitution is -define-availability so it just leads to an very akward availability definition.

@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

Copy link
Member

@compnerd compnerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

There is no `%swift-frontend-target` subsitution in test, which is
actually `%target-swift-frontend`. The wrong spelling is actually
interpreted by lit as `%swift`-frontend-target, and surprising didn't
break any tests as the last argument from subsitution is
`-define-availability` so it just leads to an very akward availability
definition.
@cachemeifyoucan cachemeifyoucan force-pushed the eng/PR-no-swift-target-frontend branch from 89b33c4 to 407674e Compare December 19, 2023 00:08
@cachemeifyoucan
Copy link
Contributor Author

@swift-ci please smoke test

@mikeash
Copy link
Contributor

mikeash commented Dec 19, 2023

That's a hilarious bug.

@cachemeifyoucan cachemeifyoucan merged commit a6c9887 into swiftlang:main Dec 19, 2023
@cachemeifyoucan cachemeifyoucan deleted the eng/PR-no-swift-target-frontend branch December 19, 2023 04:57
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.

3 participants