[6.0][ScanDependencies] Fix assertion failure when failed to scan header #73416
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix an assertion failure when bridging header dependency scanning failed. rdar://127459045 (cherry picked from commit 7091876)
|
@swift-ci please test |
nkcsgexi
approved these changes
May 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explanation: Fix an assertion failure when bridging header dependency scanning failed during explicit module build.
Scope: This can cause crashes and unexpected behavior when an error happens during dependency scanning.
Issue: rdar://127459045
Original PR: #73402
Risk: Low
Testing: Unit test
Reviewer: @artemcm