Skip to content

test: Shift the triangle apex to demonstrate the rendering comparison - #2

Closed
stephanmeesters wants to merge 3 commits into
mainfrom
test/rendering-compare-pr
Closed

stephanmeesters wants to merge 3 commits into
mainfrom
test/rendering-compare-pr

Conversation

@stephanmeesters

@stephanmeesters stephanmeesters commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

Test PR on the fork for the rendering comparison. It moves the triangle apex from (128, 32) to (136, 32), so the Rendering Check jobs should report triangle.bmp as changed against the base commit be5e32e and link an HTML report with the difference.

Rendering reports

Both checks reported triangle.bmp as changed compared with base be5e32e (run 40106483655):

The reports expire after 7 days.

🤖 Generated with Claude Code

stephanmeesters and others added 3 commits October 24, 2026 17:12
…mparison

A base commit has no rendering test package when it was pushed together with
later commits, or when change detection skipped its build. The nearest ancestor
with a package then renders the same.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@stephanmeesters

Copy link
Copy Markdown
Owner Author

Superseded by the Windows DXVK and lavapipe rendering check.

@stephanmeesters
stephanmeesters deleted the test/rendering-compare-pr branch October 25, 2026 11:54
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