-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[DependencyScan] Fix and cleanup CAS Depscanner #67133
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
[DependencyScan] Fix and cleanup CAS Depscanner #67133
Conversation
@artemcm Can you double check if my assumption in the last commit is correct? Currently, swift-driver will gets more and more command-line arguments as it tries to rescan the dependency. |
Yeah, makes sense to me, good catch! |
fcbf14f
to
101adee
Compare
@swift-ci please smoke test |
101adee
to
6e55a75
Compare
@swift-ci please smoke test |
6e55a75
to
12e227f
Compare
@swift-ci please smoke test |
12e227f
to
0a71082
Compare
@swift-ci please smoke test |
0a71082
to
a5081ad
Compare
@swift-ci please smoke test |
a5081ad
to
d9bbc93
Compare
@swift-ci please smoke test |
d9bbc93
to
ad34ae6
Compare
@swift-ci please clean smoke test |
ad34ae6
to
4276fc1
Compare
@swift-ci please smoke test |
…deps Make sure the sources for bridging header is added as part of the CAS filesystem for the main module. Even bridging header should be compiled into PCH, PCHs are not standalone that it can be used without source file.
4276fc1
to
96e0965
Compare
@swift-ci please smoke test |
Drop out the part that finalize the command-line to avoid multiple argument append since that seems to break test cases nondeterministically. It is very small fix now. Merging. |
Fix and cleanup dependency scanner for CAS.