[ iOS, macOS ] imported/w3c/web-platform-tests/css/css-backgrounds/border-image-round-and-stretch.html is a constant ImageOnly Failure.
https://bugs.webkit.org/show_bug.cgi?id=254351
Summary [ iOS, macOS ] imported/w3c/web-platform-tests/css/css-backgrounds/border-ima...
Attachments
Bri Harris
Comment 1 2023-03-23 11:18:36 PDT
I was able to replicate this failure on iOS 16 ToT as follows: run-webkit-tests imported/w3c/web-platform-tests/css/css-backgrounds/border-image-round-and-stretch.html I was also able to replicate at Ventura ToT the same way.
Radar WebKit Bug Importer
Comment 2 2023-03-23 11:19:06 PDT
Bri Harris
Comment 3 2023-03-23 14:09:34 PDT
EWS
Comment 4 2023-03-23 14:14:29 PDT
Test gardening commit 262037@main (f2b627192be8): <https://commits.webkit.org/262037@main> Reviewed commits have been landed. Closing PR #11887 and removing active labels.
Ryan Haddad
Comment 5 2023-03-23 15:53:17 PDT
It looks like this test was re-enabled with https://commits.webkit.org/261903@main. The fuzzy match metrics added with that commit seem to have made it pass on arm64 based macOS queues, but it continued to fail on x86 macOS bots as well as both arm64 and x86 iOS simulator queues. The fuzzy match change in https://commits.webkit.org/262037@main may have been too extreme and might cover up real failures.
Brent Fulgham
Comment 6 2023-03-23 15:59:12 PDT
(In reply to Ryan Haddad from comment #5) > It looks like this test was re-enabled with > https://commits.webkit.org/261903@main. > > The fuzzy match metrics added with that commit seem to have made it pass on > arm64 based macOS queues, but it continued to fail on x86 macOS bots as well > as both arm64 and x86 iOS simulator queues. > > The fuzzy match change in https://commits.webkit.org/262037@main may have > been too extreme and might cover up real failures. I think the wider fuzzy-match values are better than the original state of an expected image failure. It's frustrating that Arm and Intel have different pixel rounding on these images.
Note You need to log in before you can comment on or make changes to this bug.