Skip to content

Measure a fixed visual workload on Windows CI - #1932

Draft
bghgary wants to merge 3 commits into
BabylonJS:masterfrom
bghgary:bghgary-windows-ci-timing
Draft

bghgary wants to merge 3 commits into
BabylonJS:masterfrom
bghgary:bghgary-windows-ci-timing

Conversation

@bghgary

@bghgary bghgary commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

[Created by Copilot on behalf of @bghgary]

This draft measures Windows continuous-integration execution time for a fixed 305-scene workload, using one worker and then two disjoint workers. It is an experiment, not a full-suite migration or a change to legacy validation.

The comparison keeps Babylon.js 9.15.0, 600 × 400 images, original web references, scene metadata and image tolerances unchanged. Windows uses Release, V8 and D3D11; hardware and backend differences may produce comparison failures, which remain failures in the reports.

The workload and reference hashes are in Apps/scripts/windowsTiming/workload.json. Native source is pinned to 397d5c09ec01fce62b206ba4b68b2fc189b4f744; shared Babylon.js source is pinned to d09f642c3813c8df178215acadc27f649510675a. The experimental workflow reports build/setup separately from test execution and uploads per-scene outcomes and image differences.

bghgary and others added 3 commits October 13, 2026 11:31
Keep the timing experiment separate from full-suite migration. Pin the
native prototype, shared scene definitions, original reference hashes and
the 151/154 worker split so platform failures remain visible.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 50b024d7-d746-4f06-b4e7-094b8673be14
The earlier batch timing does not measure the current shared Playwright path. Pin the measured mobile sources and exact scene selections so hosted Windows timing can be compared without changing reference images or tolerances.

Retain every failed comparison and validate exact per-scene coverage before accepting a timing result.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 83275ca7-654f-411b-9fa9-6b0cae717308
Adding npm's packaged bin directory to PATH makes its Windows launcher look for npm-prefix.js beneath the wrong root. Use the generated node_modules/.bin launcher instead.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 83275ca7-654f-411b-9fa9-6b0cae717308
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant