-
Notifications
You must be signed in to change notification settings - Fork 10.5k
test: Improve test/Misc/verify-swift-feature-testing.test-sh
#79739
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 smoke test macOS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I was going for clarity with the multiple grep
invocations over the same set of files, but if reducing the number of grep
invocations brings the runtime to less than half, a little bit less clarity might be worth it.
I would like to know the reason for the new REQUIRES:
. I work on Linux a lot, and this script can be helpful there too (and in Windows).
19a6c59
to
ccb205b
Compare
* The set of files that enable features and the set of files that require features are expected to have a very small, if any, difference. Don't compute and check each set separately. * Find RUN and REQUIRES lines in a file in one go.
* Account for variable number of spaces. * Match strings like '-enable-upcoming-feature\'. We want to complain about these because the script cannot get the job done when the option and argument are on different lines. The capture group will match '' in these cases.
* Place 'error: ' after file name. * Be more clear about what's wrong and where.
ccb205b
to
02359f4
Compare
Thanks for the quick review! |
@swift-ci please smoke test |
Run it only on macOS.