ci(studio): the timeline viewport gate runs one pinned Chrome build, not the runner's (#7180)

The runner image ships Chrome 156.0.8078.47 or .79 run to run, and .79 renders one more thumbnail on open, so the studio-open ceilings failed on changes that never touched Studio. The ceilings file now records the major it is measured on.
This commit is contained in:
Miguel Ángel
2026-11-04 19:44:23 +00:00
committed by GitHub
parent 3d78ac0fa6
commit 2679bcdee7
2 changed files with 9 additions and 1 deletions
+8
View File
@@ -980,6 +980,14 @@ jobs:
- run: bun run --filter '@hyperframes/{parsers,lint,studio-server}' build
- run: bun run --cwd packages/core build
- run: bun run --cwd packages/core build:hyperframes-runtime
- name: Set up the Chrome build the work-count ceilings were measured on
# The runner image's Chrome moves under the gate: 156.0.8078.79 renders one more thumbnail than .47.
# Bump this with the ceilings in packages/studio/tests/e2e/perf-ceilings.json, never alone.
id: chrome
uses: browser-actions/setup-chrome@c785b87e244131f27c9f19c1a33e2ead956ab7ce # v1
with:
chrome-version: 156.0.8078.47
- run: echo "CHROME_PATH=${{ steps.chrome.outputs.chrome-path }}" >> "$GITHUB_ENV"
- name: Install the fixture as a Studio project
# Studio resolves projects from packages/studio/data/projects, which is
# gitignored. The fixture composition is tracked under tests/e2e, so