Plan: move Skip CI off Intel macOS runners

オープン
#23 コメント 10 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
リファクタリング
明瞭さ
おおむね明確
活発さ
活発
技術スタック
android, github-actions, swift, yaml

調査の方向性

Start with the linked work in #22, skiptools/skip-ffi#15, skiptools/skipstone#289, and skiptools/skipstone#290, then read the relevant skip-framework.yml workflow and the PRs' runner and test-coverage notes. The issue is a multi-repository migration plan, with some work blocked; check each step's status and runner constraints before taking one on. Done means each migration preserves the tests it previously ran and the stated blocked work is resolved before changing the default runner.

索引モデルが issue の本文から書いたものです。

説明

This tracks moving Skip's CI off Intel macOS runners. The PRs below link here; each one stands on its own and keeps every test it ran before.

Why

  • Speed. The same work runs much faster off Intel. skip-ffi's macOS job: 24–40 min on macos-26-intel, 8 min on arm macos-26. skipstone android-ci's slowest path: 161–163 min, 75–106 min with this plan.
  • Queues. skiptools repos share one pool of concurrent macOS jobs. Intel jobs waited 10–56 min (skip-ffi) and up to 7.9 h (skipstone) before starting. Every macOS minute saved shortens that queue for every repo.
  • Direction. GitHub announced the end of x86_64 macOS runners (then dated fall 2027), as Apple has dropped the architecture. macos-26-intel has since shipped with no end date, so this is a direction rather than a deadline.

Constraints

  • No Android emulator on arm macOS runners. No nested virtualization: HVF error: HV_UNSUPPORTED on macos-15 and macos-26, API 28 and 34 (probe). Emulator tests run on ubuntu-24.04 (KVM).
  • Not everything builds on Linux yet. Fuse (skip-android-bridge), and the host swift test of skip-ui (CoreGraphics) and skip-fuse-ui (duplicate static products). Those emulator tests stay on Intel for now.

Steps

Merge order matters for the first two.

  • #22: skip-framework.yml skips its emulator steps on arm64. Its guard read env.RUNNER_ARCH, which is always empty, so no caller could move its macOS job to arm. Needs a v1 tag update.
  • skiptools/skip-ffi#15: macos-26 + Ubuntu, after #22 is in v1. Its emulator tests already ran on Ubuntu; the Intel duplicate goes. Run: 11.5 min, set by the Ubuntu job.
  • skiptools/skipstone#289 (superseded by skiptools/skipstone#300): android-ci on macos-26 + Ubuntu + one macos-26-intel leg for the Fuse emulator test. 4 Intel jobs → 2; macOS minutes per run 524 → 217–310.
  • skiptools/skipstone#290: the Linux skip binary segfaulted transpiling SkipUI (musl's 128 KiB thread stacks). With 8 MiB, skip android build works on Linux: skip-ui 32 s vs 91 s on Intel, skip-fuse-ui 57 s vs 180 s.
  • Blocked: skip-ui and skip-fuse-ui on ['macos-26', 'ubuntu-24.04'], until their host swift test builds on Linux. Measured so far: on arm macos-26, their iOS, export and Robolectric work takes 20 / 43 min; the Intel job, which also runs the emulator tests, takes 47 / 89 min.
  • Later: change skip-framework.yml's default runs-on (at least 43 callers), once the above has run for a while.

How coverage was checked

For each PR, the last green upstream run against a fork run of the branch: executed tests per kind (host swift test, Robolectric, iOS, emulator) and per runner, counted from the job logs. Every test that ran before still runs; where one changed runner (emulator tests now only on Ubuntu), the PR says so.

🤖 Generated with Claude Code

主要言語
言語のデータがありません
スター
0
フォーク
7
平均マージ
29分
マージ済み PR(30日)
1

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

似ている issue

Build System の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。