-
Notifications
You must be signed in to change notification settings - Fork 10.4k
raylib screenshots: fix and include pair device screenshot #36394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
raylib screenshots: fix and include pair device screenshot #36394
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes the pair device screenshot functionality in the raylib UI tests and includes it in the screenshot comparison workflow while skipping its diff check. The changes ensure the pair device screen is properly navigated to and captured, while preventing CI failures from expected differences in this screen.
Key Changes:
- Updated the setup function for pair device screenshots to use the correct navigation path
- Modified the GitHub workflow to include pair_device screenshots in the output but skip their diff comparison
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| selfdrive/ui/tests/test_ui/raylib_screenshots.py | Fixed navigation to pair device screen by calling setup_settings first and adjusting click coordinates |
| .github/workflows/ui_preview.yaml | Removed grep filter and added conditional logic to skip diff check for pair_device screenshots |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Bruh I've been modifying the old ui_preview workflow, no wonder it wasn't working 🤦 |
|
I can't make it work :( |

























#36393, but should also include the screenshot in the list of all screenshots, only skipping the diff check.
There were reports of a QR code error, so it would be nice to know if that happens.
.