An open source design system that's fully customizable and agent ready
TypeScript
perf(ci): give the heavier test lane the larger runner (#6080)
sangwook20d1a4084f66
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.ymlindex 7ebcd63414..45f040c4bb 100644--- a/.github/workflows/ci.yml+++ b/.github/workflows/ci.yml@@ -180,13 +180,14 @@ jobs:## The projects are independent by construction (see vitest.config.ts: `ui` is# jsdom + StyleX, `node` is everything else), so running them as two jobs- # costs no duplicate execution and each lane carries roughly half the work.- # `node` is the heavier lane — locally 570s against the ui project's 244s —- # so it takes the larger supported runner while `ui` stays on the 2-core arm- # box.+ # costs no duplicate execution. They do NOT carry half the work each: on this+ # CI, `ui` is ~5x the heavier lane, so it takes the larger runner.#- # The repo-wide guardrail steps ride the LIGHTER lane, so the slow one is- # nothing but tests.+ # The earlier local figure that put `node` ahead (570s vs 244s) was not a+ # comparable measurement — only the node run was bounded to a small worker+ # pool, and node is the project whose cost is per-assertion CLI subprocesses.+ #+ # The repo-wide guardrail steps ride `test-ui` (~18s of it).## `test` remains a job, so the required check of that name still exists and# still reports for every PR. This mirrors the `build` join over@@ -194,7 +195,7 @@ jobs:test-ui:needs: [check-scope]if: ${{ always() && !cancelled() }}- runs-on: 2-core-ubuntu-arm+ runs-on: 4-core-ubuntupermissions:contents: readsteps:@@ -252,7 +253,7 @@ jobs:test-node:needs: [check-scope]if: ${{ always() && !cancelled() }}- runs-on: 4-core-ubuntu+ runs-on: 2-core-ubuntu-armpermissions:contents: readsteps:diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.ymlindex 4fd5f8cf06..46f983675b 100644--- a/.github/workflows/deploy.yml+++ b/.github/workflows/deploy.yml@@ -79,8 +79,11 @@ jobs:# independent by construction (vitest.config.ts), so they split cleanly; the# typecheck gates need the `pnpm build` they follow, so they stay together in# their own lane and take the build with them.+ #+ # `ui` is the heavier project by ~4x here, so it takes the larger runner (see+ # ci.yml's lane comment).test-ui:- runs-on: 2-core-ubuntu-arm+ runs-on: 4-core-ubuntupermissions:contents: readsteps:@@ -93,7 +96,7 @@ jobs:- run: pnpm vitest run --project uitest-node:- runs-on: 4-core-ubuntu+ runs-on: 2-core-ubuntu-armpermissions:contents: readsteps: