Skip to content

Update visual baselines (main) - #535

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
visual-baselines/main
Closed

Update visual baselines (main)#535
github-actions[bot] wants to merge 1 commit into
mainfrom
visual-baselines/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Regenerated visual-regression baselines via the update visual baselines workflow (generation sharded across parallel runners).

Review checklist

  • Open the "Files changed" tab and inspect each PNG diff
  • Confirm the visual changes match an intentional UI change
  • If a baseline looks wrong, close this PR and investigate before re-running the workflow

Partial-update guard: baselines are regenerated in parallel shards. If any update shard failed (e.g. an EWC backend wedge), this PR is missing that shard's specs. Check the triggering run for failed shards and re-run the workflow to fill any gap before merging.

Once merged, future tests.yml runs on main will compare against these baselines.


Generated by run #30

@github-actions
github-actions Bot force-pushed the visual-baselines/main branch from b98da54 to baa91f4 Compare September 9, 2026 07:20
@sloorush sloorush closed this Sep 9, 2026
@sloorush
sloorush deleted the visual-baselines/main branch September 9, 2026 07:55
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