Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Re-enable test-android on main once the self-hosted runner is back

未关闭 适合新手
#379 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
66/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
github-actions
领域
ci-cd

调研方向

从 .github/workflows/check.yml 中的 test-android job 开始,检查最近的 Check 运行记录,以确认 ubuntu-self-hosted 是否在线。runner 或替代者准备就绪后,恢复 main-branch 条件并删除临时注释。完成的标准是 Android 在 main 上运行,并且 Check workflow 报告为绿色。

由索引模型根据 Issue 内容生成。

描述

Android 🤖

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-hosted runner is back online (or migrate the job to a GitHub-hosted ubuntu-latest runner with KVM for the emulator).
  • Restore the github.ref == 'refs/heads/main' condition on test-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.
主要语言
TypeScript
星标
188
派生
10
平均合并
2 天 17 小时
30 天内合并 PR
3

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/react-native-node-api 的其他 Issue

查看 callstackincubator/react-native-node-api 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。