-
-
Notifications
You must be signed in to change notification settings - Fork 685
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
Test App Icon failure in testbed #3021
Comments
I suspect this may have something to do with sizing - the test technique is based upon pixel picking, but if the icon is a different size, then the pixel being picked might end up touching a border (or something similar) that has a radically different red value. If we can't find a reliable fix for picking the same pixel every time (or pick a location that isn't subject to this sort of problem), a "soft" match sounds like a plausible workaround.
As long as you've got the upstream repo as a remote, I can't think of any reason why this would be happening. |
This has always been a bit mysterious to me as well, but you might need to run |
I've tried that too. Ah well, it's not particularly a problem, just mysterious and mildly inconvenient. |
Describe the bug
I keep forgetting to post this, but it's been happening consistently for a while on my computer, despite the fact I've never seen it pop up in CI.
test_app_icon
always fails, apparently because the pixel being tested is off by 1 in the green band. It's(149, 118, 75, 255)
, while one of the acceptable values is(149, 119, 73, 255)
.Steps to reproduce
briefcase dev --test -- tests/app/test_app.py::test_app_icon
(Same with briefcase run)
Expected behavior
I'd expect it to pass, like in CI.
Screenshots
No response
Environment
Logs
Additional context
I see this comment in the test:
Perhaps we could test within an acceptable range for each band, rather than expecting one of the discrete sets of values listed... It's odd that each band only varies by a little bit in the acceptable values for each of the three tests, except for the explicit icon's mid color's red value, which ranges from 0 to 105.
(Speaking of testing with 0.4.8, would there be any reason why the 0.4.8 tag is missing from my repo, even after a
fetch --all
? The latest one I have is 0.4.7, but I can manually check out commit b987e88. And I can't fetch any tags for Travertino at all.)The text was updated successfully, but these errors were encountered: