Re-enable test-android on main once the self-hosted runner is back
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Start in .github/workflows/check.yml at the test-android job and inspect recent Check runs to confirm whether ubuntu-self-hosted is online. Restore the main-branch condition and remove the temporary comment once the runner or replacement is ready. Done means Android runs on main and the Check workflow reports green.
Written by the indexing model from the issue text.
Description
Context
The test-android job in check.yml runs on ubuntu-self-hosted. That runner is currently offline — the job sits in queued indefinitely (observed 6h+ on 2026-07-18). Because it never starts, the whole Check run on main never completes, which blocks main from ever reporting green.
As a stopgap, the job's if was changed from:
if: github.ref == 'refs/heads/main' || contains(github.event.pull_request.labels.*.name, 'Android 🤖')
to run only on PRs labeled Android 🤖, removing it from main pushes. This means Android is no longer exercised on main automatically.
To re-enable
- Confirm the
ubuntu-self-hostedrunner is back online (or migrate the job to a GitHub-hostedubuntu-latestrunner with KVM for the emulator). - Restore the
github.ref == 'refs/heads/main'condition ontest-android. - Remove the temporary comment added above the
if.
Notes
- Also consider whether the job should be moved off self-hosted entirely to avoid this failure mode recurring — GitHub-hosted Ubuntu runners now support nested virtualization (KVM) for Android emulators.
- Dominant language
- TypeScript
- Stars
- 188
- Forks
- 10
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstackincubator/react-native-node-api
-
Sanity check of Hermes source directory via environment variable, when building Android projects OpenAndroid 🤖 good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/react-native-node-api#163 · 1 comment ·
-
enhancement good first issue gyp-to-cmake
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstackincubator/react-native-node-api#161 · 3 comments · 1 reaction ·
-
enhancement Host 🏡
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Automatable good first issue
Difficulty 3/5 1-2 days Newbie friendliness 15/100
callstackincubator/react-native-node-api#424 · 1 comment ·
-
gyp-to-cmake
Difficulty 4/5 3-5 days Newbie friendliness 55/100
callstackincubator/react-native-node-api#423 · 1 comment ·
All issues in callstackincubator/react-native-node-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·