perf(ci): attribute the Run tests step critical path
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github-actions, typescript
- 領域
- ci-cd, performance, testing
研究方向
Start with the Run tests step in .github/workflows/squad-ci.yml (lines 93-195) and the Vitest settings in vitest.config.ts (lines 10-17). Read the audited timing evidence in the issue, then reproduce the step timings with gh run view. Done means three retry-disabled profiles with per-file timing data, test-count inventory, and one evidenced bottleneck or a documented no-candidate result. Coordinate with the parent issue and the listed owner before starting.
由索引模型根據 Issue 內容生成。
描述
Summary
Recent successful development-branch CI runs spend substantially more time executing tests than building or installing dependencies. This issue is limited to profiling that test step; these observations do not establish that sharding or increasing concurrency will help.
Proposed primary owner: release-engineer.
Observed hosted-run evidence
Observed 2026-11-12 from GitHub job/step start/end timestamps in .github/workflows/squad-ci.yml:
| Successful dev run | Test job | Run tests step | Build | Root dependency install |
|---|---|---|---|---|
| 43226523596 | 420 s | 301 s | 8 s | 28 s |
| 43224800067 | 464 s | 328 s | 9 s | 35 s |
| 43215389047 | 560 s | 394 s | 13 s | 44 s |
Median test execution is 328 seconds; median full test job is 464 seconds. These are the three most recent successful completed dev runs returned at observation time. An intervening cancelled run was excluded, not treated as a successful timing.
Reproduce the timing extraction with gh run view <run-id> --repo github/squad --json jobs,headSha,url, subtracting each job/step's startedAt from completedAt. The runs have different commits/runners and one-second timestamp resolution. This small success-only sample is observational, not controlled A/B evidence or a CI reliability estimate; step medians do not reconstruct workflow elapsed time.
Relevant source at audited revision 47082a81799710c3e457b594123d190c00596ebf: squad-ci.yml:93-195, vitest.config.ts:10-17.
Scope
Parent: github/squad#2481.
Profiling-only: attribute the existing Vitest Run tests step in squad-ci.yml. This issue ends with measured attribution and at most one proposed follow-up, not a broad CI optimization project.
Out of scope: sharding, worker-count tuning, browser/dependency caches, build/release workflows, test removal, permanent scheduling infrastructure and applying an optimization before a specific bottleneck is established.
Measurable acceptance and tests
- Capture three completed, retry-disabled profiles of the same selected SHA/test inventory on the same hosted-runner class. Record cache state, worker settings, run IDs and failures; do not replace failed attempts invisibly.
- Publish machine-readable per-file test/collection/transform/setup duration data where available and a top-ten contributor table. Report wall time, overlap and unattributed time explicitly; do not sum overlapping worker durations as elapsed time.
- Publish selected/executed/passed/failed/skipped counts and coverage inventory alongside the existing workflow baseline. Instrumentation must not change test selection, assertions, coverage or profile/worktree safety guards.
- Record
Run testselapsed time, total job/workflow elapsed time, Actions minutes and peak resources; any unavailable metric remains unknown rather than zero. - Focused collector/report tests cover an absent/truncated profile, nonzero test exit and overlapping durations; failures cannot become success-shaped reports.
- Close with one evidenced bottleneck and a separately scoped optimization proposal, or a documented no-material-candidate result. No speedup is required or claimed by this attribution issue; implementation needs its own focused acceptance criteria.
Related work and non-goals
Closed github/squad#872 addressed runner consolidation; github/squad#2284 addressed timeout/browser-cache mitigation. This is a focused execution-critical-path investigation, not reopening those changes or prescribing blind parallelism.
Methodology: microsoft/waza#846 and dotnet/aspnetcore#70219.
- 主要語言
- TypeScript
- 星號
- 3.4k
- 分支
- 516
- 平均合併
- 1 天 15 小時
- 30 天內合併 PR
- 116
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/squad 的其他 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 77/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
相似的 Issue
-
bot:ai-assisted component:platform-js status:untriaged
難度 1/5 1 小時以內 新手友好度 74/100
midnightntwrk/platform-js#38 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
ranxianglei/billion-context#7068 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
難度 2/5 1-3 小時 新手友好度 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
ilan-pinto/roaring-lions#1552 ·
維護者通常 1 天內回覆