Conversation
meta-cla
Bot
added
the
CLA Signed
cortinico
force-pushed
the
export-D122967026
branch
3 times, most recently
from
October 2, 2026 07:58
9fccf9d to
7ba1860
Compare
Summary: Two unrelated iOS CI jobs failed on `main` commit `cd2de187e8878119896159371225acbb9dfa5d9c`. The commit itself only changed Android autolinking code, so neither failure was attributable to its product change. This patch hardens the two affected CI paths without weakening their final failure semantics. ### Dynamic-framework Bundler setup Failed job: https://github.com/react/react-native/actions/runs/36918732275/job/110559233737 The Debug dynamic-framework job failed while `ruby/setup-ruby` was performing its implicit one-shot Bundler installation. Its Release sibling passed in the same workflow, and both lanes passed on the immediately preceding `main` commit. That evidence points to a transient RubyGems/Bundler setup failure rather than a deterministic React Native regression. Disable the implicit installation with `bundler: none`, read the exact pinned Bundler version from `Gemfile.lock`, and install it with three bounded attempts and 10-/20-second backoff. The script fails immediately if the lockfile version cannot be determined, and persistent installation failures remain red after the third attempt. ### E2E hosted-runner loss Failed job: https://github.com/react/react-native/actions/runs/36918732275/job/110577294552 The Release E2E matrix cell lost communication with its GitHub-hosted runner before reaching the step that writes its explicit status output. The downstream report job checked only that output. Because runner loss left the output empty rather than setting it to `failure`, the report job incorrectly emitted success and skipped the existing fresh-runner retry chain. Also inspect `needs.test.result`. Any non-successful matrix result now propagates failure and activates the existing retry jobs, while successful jobs and explicit test failures retain their previous behaviour. This changes failure reporting only; it does not alter E2E test execution. Changelog: [Internal] Differential Revision: D122967026
cortinico
force-pushed
the
export-D122967026
branch
from
October 2, 2026 09:09
7ba1860 to
9807f48
Compare
|
@cortinico has exported this pull request. If you are a Meta employee, you can view the originating Diff in D122967026. |
|
This pull request has been merged in c69c54a. |
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
1 participant
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:
Two unrelated iOS CI jobs failed on
maincommitcd2de187e8878119896159371225acbb9dfa5d9c. The commit itself only changed Android autolinking code, so neither failure was attributable to its product change. This patch hardens the two affected CI paths without weakening their final failure semantics.Dynamic-framework Bundler setup
Failed job: https://github.com/react/react-native/actions/runs/36918732275/job/110559233737
The Debug dynamic-framework job failed while
ruby/setup-rubywas performing its implicit one-shot Bundler installation. Its Release sibling passed in the same workflow, and both lanes passed on the immediately precedingmaincommit. That evidence points to a transient RubyGems/Bundler setup failure rather than a deterministic React Native regression.Disable the implicit installation with
bundler: none, read the exact pinned Bundler version fromGemfile.lock, and install it with three bounded attempts and 10-/20-second backoff. The script fails immediately if the lockfile version cannot be determined, and persistent installation failures remain red after the third attempt.E2E hosted-runner loss
Failed job: https://github.com/react/react-native/actions/runs/36918732275/job/110577294552
The Release E2E matrix cell lost communication with its GitHub-hosted runner before reaching the step that writes its explicit status output. The downstream report job checked only that output. Because runner loss left the output empty rather than setting it to
failure, the report job incorrectly emitted success and skipped the existing fresh-runner retry chain.Also inspect
needs.test.result. Any non-successful matrix result now propagates failure and activates the existing retry jobs, while successful jobs and explicit test failures retain their previous behaviour. This changes failure reporting only; it does not alter E2E test execution.Changelog: [Internal]
Differential Revision: D122967026