Plan: move Skip CI off Intel macOS runners
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Refactoring
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- android, github-actions, swift, yaml
- Ambito
- build-system, ci-cd, devops
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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 armmacos-26. skipstoneandroid-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-intelhas 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_UNSUPPORTEDonmacos-15andmacos-26, API 28 and 34 (probe). Emulator tests run onubuntu-24.04(KVM). - Not everything builds on Linux yet. Fuse (skip-android-bridge), and the host
swift testof 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.ymlskips its emulator steps on arm64. Its guard readenv.RUNNER_ARCH, which is always empty, so no caller could move its macOS job to arm. Needs av1tag update. - skiptools/skip-ffi#15:
macos-26+ Ubuntu, after #22 is inv1. 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-cionmacos-26+ Ubuntu + onemacos-26-intelleg 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 buildworks 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 hostswift testbuilds on Linux. Measured so far: on armmacos-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 defaultruns-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
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 0
- Fork
- 7
- Merge medio
- 29m
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
prio:low type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
NatronGitHub/Natron#1638 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
ci good first issue tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
Haseeb-MernStack/commune#133 ·
I maintainer di solito rispondono entro 1 giorno
-
difficulty: beginner dx good first issue help wanted web
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
Yormee-103/PayLoop#158 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 Meno di un'ora Idoneità per principianti 70/100