Repository navigation
Measure spec timings and share browsers in blueprint specs #262
Description
Scene's spec time is not measured anywhere today. Neither .NET Build nor JavaScript Build has run on main (both are triggered by PRs or manually), and no job keeps per-project or per-class timings. Speed work therefore has no baseline.
What looks expensive (unverified)
.github/workflows/javascript-build.yml:90-108runs 17 browser workspace spec commands one after another.- The blueprint fixtures cache bundling but launch Chromium per fixture, for example
Source/JavaScript/blueprint.administration/for_administrationApplication/given/a_administration_page.ts:58,92. - .NET:
Engine.SpecsandModel.Specs. No host-per-class or Docker-per-class pattern was found.
Proposed work
- Record timings: emit trx/junit reports from both workflows, upload them as artifacts, and add a one-line per-project summary to the job summary.
- Measure the browser specs locally per workspace. Where Chromium startup dominates, share one browser per worker and give each fixture its own context.
- Then run the browser workspaces as a bounded matrix (for example 3 shards) instead of serially.
Status
State: Done — Merged in #271; closed as completed.
Branch: arc-3152-system-execution-identity
Scope: L44: record spec timings in CI, then share browsers per worker in the blueprint browser specs. Delivered to the Scene owner (L32).
Plan: Opt-in JUnit/TRX reports uploaded with 3-day retention, plus a per-project job summary. Browser specs run as a 3-shard matrix. One shared Chromium server only in primereact and blueprint.default, where fixtures launch Chromium many times; it stays only if it saves time. The 300 ms settle wait dominates blueprint app specs and is left as a follow-up.
Delivered: - #271
Remaining: To be confirmed.
Follow-ups: None.
Activity
woksin commentedon Oct 23, 2026
Frontend timing baseline (origin/main c49522c, macOS dev machine, cold worktree, wall time excludes queueing):
yarn build(cold / warm)yarn lintyarn test(25 workspaces, jsdom/node)yarn test: vitest itself reports 167 s summed over 25 workspaces.run-task-on-workspaces.jsrunsyarn testper workspace serially (spawnSync), so the total is the sum. Largest: blueprint.default 26.6 s, blueprint.crm 14.5 s, primereact 12.5 s, blueprint.customer-portal 11.9 s, then a long tail of 4–8 s runs where transform/import is often more than half.Browser specs (
test:browser, Chromium via Playwright):Cheapest wins, in order:
projectsrun) instead of serialspawnSync. This alone should moveyarn testfrom about 198 s toward the largest single workspace.woksin commentedon Oct 25, 2026
Delivered in #271 (merged). The spec runs now report per-package timings, and the browser specs run in balanced shards. Sharing one Chromium instance across packages was measured and not kept, because it did not give a meaningful gain.