WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
221618
Drop pixel test support
https://bugs.webkit.org/show_bug.cgi?id=221618
Summary
Drop pixel test support
Sam Sneddon [:gsnedders]
Reported
2021-02-09 11:11:35 PST
With
bug 121112
never having been resolved, ever since Blink forked the pixel tests (i.e., -expected.png) haven't been run. Given this is now nearly eight years ago, it would be nice to acknowledge we aren't running the pixel tests (and that the expectations haven't been updated in equally long) and drop support for running them from run-webkit-tests.
Attachments
Add attachment
proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1
2021-02-09 11:29:16 PST
I think I'm OK with removing expected.png files, but I'm hesitant about removing support for run-webkit-tests --pixel, because there might be times where a developer wants to do before/after pixel testing of a change by rebasing pixel results first, then running tests.
Alexey Proskuryakov
Comment 2
2021-02-09 11:48:32 PST
What's been stopping us before was that even though pixel tests couldn't meaningfully run, referring to an ancient -expected.png file provided insight into what a test was meant to do.
Sam Sneddon [:gsnedders]
Comment 3
2021-02-10 05:57:48 PST
(In reply to Simon Fraser (smfr) from
comment #1
)
> I think I'm OK with removing expected.png files, but I'm hesitant about > removing support for run-webkit-tests --pixel, because there might be times > where a developer wants to do before/after pixel testing of a change by > rebasing pixel results first, then running tests.
FWIW, I have some concern about our ability to keep all that code working when it isn't running on any bot, hence I somewhat question the value of keeping it around if we're never actually running it. There's enough scattered around various parts of the codebase it feels somewhat fragile. If we _do_ want to keep it, I'd rather we started running at the very least a small number of pixel tests in CI. (Though I don't much like the idea of running them at all, given how fragile they are!) (In reply to Alexey Proskuryakov from
comment #2
)
> What's been stopping us before was that even though pixel tests couldn't > meaningfully run, referring to an ancient -expected.png file provided > insight into what a test was meant to do.
My proposal here was to just remove the support from run-webkit-tests, and not necessarily do anything about the -expected.png files (which IIRC Myles saw value in, for the reason you say).
Fujii Hironori
Comment 4
2021-02-11 12:20:28 PST
Even though no ports enable pixel tests as default, they are still used by enabling -p switch explicitly on developers PC. For example,
r272361
,
r270756
and
r269072
.
Sam Sneddon [:gsnedders]
Comment 5
2021-02-12 04:56:51 PST
Okay, if people are still definitely using them, then WONTFIX.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug