-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Generate scripts for component-wise lit invocations #30673
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
cc @gribozavr |
With this change, the test directory will contain 3 scripts: * swift-check-silgen.sh (runs lit.py on test/SILGen as well as any directory containing a file that has "silgen" string in its name.) * swift-check-irgen.sh (runs lit.py on test/IRGen as well as any directory containing a file that has "irgen" string in its name.) * swift-check-typecheck.sh (runs lit.py on test/SEMA as well as any directory containing a file that has "typecheck" in its name.)
WDYT about slightly different semantics, "runs lit.py on test/SILGen as well as any test file that has 'silgen' in its name"? |
@scentini fixed it in the latest commit that uses |
@swift-ci Please smoke test |
An alternative approach: enhancing |
This is no longer needed right? |
I believe that #30850 was deemed sufficient. Closing the PR |
With this change, the test directory will contain 3 scripts:
swift-check-silgen.sh
(runs lit.py ontest/SILGen
as well as any directory containing a file that has'silgen'
string in its name.)swift-check-irgen.sh
(runs lit.py ontest/IRGen
as well as any directory containing a file that has'irgen'
string in its name.)swift-check-typecheck.sh
(runs lit.py ontest/Sema
as well as any directory containing a file that has'typecheck'
in its name.)