-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Invoke build tool plugins based on allTargets
#6776
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 |
@swift-ci smoke test linux |
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.
Can a test for this be added?
Currently, we're only invoking build tool plugins for reachable targets which does not seem correct based on the fact that we're willing to build targets out of reachable, e.g. when executing a command plugin. rdar://113264168
695fd11
to
3a8dbfa
Compare
@swift-ci please test |
Not really sure how to add a test case for this since it requires a quite elaborate setup to demonstrate the original issue. I think that's ok though since using |
would be possible to add a test? |
See comment above. In principle yes, but the cost seems high for something that's obviously just wrong. |
Currently, we're only invoking build tool plugins for reachable targets which does not seem correct based on the fact that we're willing to build targets out of reachable, e.g. when executing a command plugin. rdar://113264168
Currently, we're only invoking build tool plugins for reachable targets which does not seem correct based on the fact that we're willing to build targets out of reachable, e.g. when executing a command plugin. rdar://113264168
Currently, we're only invoking build tool plugins for reachable targets which does not seem correct based on the fact that we're willing to build targets out of reachable, e.g. when executing a command plugin.
rdar://113264168