Skip to content

chore(test): per-file test timing in CI (diagnostic, do not merge) - #10844

Draft
chrisgervang wants to merge 2 commits into
masterfrom
chr/test-timing-reporter
Draft

chrisgervang wants to merge 2 commits into
masterfrom
chr/test-timing-reporter

Conversation

@chrisgervang

Copy link
Copy Markdown
Collaborator

Background

CI's test-coverage job takes about 8 minutes. Some headless tests take 15–18s on CI but well under 1s when run alone, so the cost depends on run order or shared state. This draft gathers clean CI numbers before any fix. It is not meant to be merged.

Change List

  • test/setup/timing-reporter.ts prints per-file import and test time in run order, plus the slowest files and tests, to the log and the job summary
  • vitest.config.ts registers the reporter
  • Next: push the terrain-extension-drape speedup (draped GeoJsonLayer without strokes) to compare against this baseline

Temporary diagnostic reporter to find where CI test time goes. Not intended to merge.
Draping strokes under SwiftShader took several hundred ms of GPU time per terrain tile, making this the slowest render test. Golden image regenerated without strokes.
@coveralls

coveralls commented Oct 11, 2026 •

Copy link
Copy Markdown

Coverage Status

coverage: 83.503% (-0.01%) from 83.517% — chr/test-timing-reporter into master

This branch has not been deployed

No deployments
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.

2 participants