perf(ci): attribute the Run tests step critical path

Đang mở
#2,478 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
25/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
github-actions, typescript
Lĩnh vực
ci-cd, performance, testing

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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 tests elapsed 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.

Ngôn ngữ chính
TypeScript
Star
3.4k
Fork
516
Merge trung bình
1 ngày 15 giờ
Pull request đã merge (30 ngày)
116

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của github/squad

Tất cả issue của github/squad

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.