Repository navigation
Conversation
This branch has not been deployed
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
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.
Summary:
The default-branch
Test Allrun for commit9b7c956c356f0257adf453ff5791b6508f5ab869hit an Apple clang frontend crash while compilingRNTMyNativeViewComponentView.mmwith Xcode 16.4:clang: error: unable to execute command: Segmentation fault: 11clang: error: clang frontend command failed due to signalThat build never uploaded
RNTesterApp-NewArch-Debug, so the downstream Debug E2E check also failed while downloading the missing artifact. The parent commit and the preceding 14 sampledtest_ios_rntester (Debug, false)jobs passed, including the same compiler invocation on the parent SHA. The only commit in the chronological range (cca720709a74c797f30df9e6a96832fabc88c8d5..9b7c956c356f0257adf453ff5791b6508f5ab869) changes Android test-helper names and comments/documentation; it does not change the failing Objective-C++ source. This makes a hosted compiler crash much more likely than a deterministic source regression, although a local Xcode 16.4 reproduction was not available.This change retries the RNTester build once only when both observed Apple clang crash signatures are present. It removes DerivedData before retrying. Other build failures are not retried, and a repeated clang crash still fails the job.
Failure: https://github.com/react/react-native/actions/runs/38760856731/job/116533978498
Dependent missing-artifact failure: https://github.com/react/react-native/actions/runs/38760856731/job/116538539515
Risk / limitations: The retry is intentionally limited to this exact compiler-crash signature and one additional attempt. It does not address the underlying Apple clang defect. Full RNTester reproduction was not practical locally because the available machine has Xcode 26.6 rather than the hosted Xcode 16.4 environment.
Changelog:
[INTERNAL] [FIXED] - Retry the RNTester iOS build once when Apple clang itself crashes.
Test Plan:
git diff --check— passed..github/actions/test-ios-rntester/action.ymlwith Ruby's YAML parser — passed.Build RNTestershell block with a fakexcodebuildin four scenarios: