Skip to content

Revert "Unbreak android CI by moving to ubuntu-latest (#57216)"#57323

Draft
cortinico wants to merge 1 commit into
mainfrom
nc/ubuntu-runners
Draft

Revert "Unbreak android CI by moving to ubuntu-latest (#57216)"#57323
cortinico wants to merge 1 commit into
mainfrom
nc/ubuntu-runners

Conversation

@cortinico

@cortinico cortinico commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Summary

This reverts the runner changes from #57216, which moved the Android CI jobs from the dedicated 4-core-ubuntu / 8-core-ubuntu runners onto the standard ubuntu-latest runners.

I'm opening this (as a draft) to see if we can speed up the RN runners — i.e. to measure whether going back to the larger dedicated runners gives us faster CI than ubuntu-latest. This is an experiment to compare timings.

What's reverted

  • e2e-android-rntester.yml: ubuntu-latest4-core-ubuntu
  • e2e-android-templateapp.yml: ubuntu-latest4-core-ubuntu
  • fantom-tests.yml: ubuntu-latest8-core-ubuntu
  • test-all.yml: build_fantom_runner, build_android, build_npm_package8-core-ubuntu; test_android_helloworld4-core-ubuntu

Not reverted (drift since #57216)

  • nightly.yml was deleted on main (consolidated into publish-npm.yml).
  • publish-npm.yml was fully restructured on main (the old publish-react-native reusable job no longer exists).

These two are release/nightly jobs rather than the per-PR CI that determines runner speed, so they're intentionally left untouched.

Changelog:

[INTERNAL] -

Changelog

[INTERNAL] -

Test Plan

CI — compare job durations against ubuntu-latest.

This reverts the runner changes from #57216, moving the Android CI jobs
back from `ubuntu-latest` to the dedicated `4-core-ubuntu` / `8-core-ubuntu`
runners.

Goal: measure whether the dedicated runners speed up RN's CI compared to
`ubuntu-latest`.

Note: `nightly.yml` was deleted and `publish-npm.yml` was restructured on
main since #57216 landed, so those two files are intentionally left
untouched; this revert only covers the per-PR CI jobs.
@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. p: Facebook Partner: Facebook Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant