Skip to content

Protect the add_dependencies calls against non-existent targets #71348

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

Merged
merged 1 commit into from
Feb 3, 2024

Conversation

etcwilde
Copy link
Member

@etcwilde etcwilde commented Feb 2, 2024

The install target is sometimes the None target, which doesn't actually exist. This should perhaps be spelled never_install instead, but given that these are random names, we should protect the add_dependencies calls to only accept install components that actually exist.

Fixes: rdar://122194103

The install target is sometimes the `None` target, which doesn't
actually exist. This should perhaps be spelled `never_install` instead,
but given that these are random names, we should protect the
`add_dependencies` calls to only accept install components that actually
exist.
@etcwilde etcwilde requested a review from drodriguez February 2, 2024 18:55
@etcwilde etcwilde requested a review from a team as a code owner February 2, 2024 18:55
@etcwilde
Copy link
Member Author

etcwilde commented Feb 2, 2024

@swift-ci please test

@etcwilde etcwilde requested a review from compnerd February 2, 2024 18:56
@etcwilde etcwilde enabled auto-merge February 2, 2024 20:51
@etcwilde etcwilde merged commit 5f8da9e into swiftlang:main Feb 3, 2024
@etcwilde etcwilde deleted the ewilde/protect-the-dependents branch February 4, 2024 06:14
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.

2 participants