1982937 - wpt reftest svg/text/reftests/text-bidi-controls-anchors-2.svg fails on Android 14 emulator

Status: NEW

(Core :: SVG, defect)

Description

[Daniel Holbert [:dholbert]]

Spinning off a bug for a reftest failure in this run on the new new android 14 emulator image:

https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=fdea14904f15d8fe3a01e1277a1ad60054bf5e8e&test_paths=%2Fsvg%2Ftext%2Freftests&selectedTaskRun=Z-kfyLChTHePkImjhiZq7w.0

The WPT svg/text/reftests/text-bidi-controls-anchors-2.svg fails with some fuzziness as shown here:

reftest-analyzer shows "Maximum difference per channel 64, 78 pixels differ"

We can just add a .ini annotation to allow that fuzzy tolerance, I think.

(Note: bug 1982907 covers the other fuzzy failure there, and bug 1982914 covers the fatal assertion-failure (crash) in text-context-fill.svg.)

Comment 1

[Jamie Nicol [:jnicol]]

The test is already marked as fuzzy:
https://searchfox.org/mozilla-central/rev/ace4c0612207f29c0d0530dec82e15aeb5fe17d5/testing/web-platform/tests/css/css-sizing/aspect-ratio/replaced-element-003.html#6-8
...but we're varying by 64 on the antialiased pixels which is beyond the hardcoded fuzzy tolerance of 30.

We can just add a .ini annotation to allow a maxDifference of up to 64 on Android, I think.

The link appears to show the other test replaced-element-003 as currently being marked as fuzzy, not text-bidi-controls-anchors-2.svg. Is text-bidi-controls-anchors-2.svg marked as fuzzy elsewhere and you just copy-pasted the wrong link?

Comment 2

[Daniel Holbert [:dholbert]]

Ah, good catch; yeah, text-bidi-controls-anchors-2.svg is not currently marked as fuzzy after all, as far as I can tell. There was an earlier copypaste typo in bug 1982914 that I was trying to clean up after, and it looks like I got my test files mixed up as part of that, and was looking at the wrong test when I found the fuzzy annotation.

I'll edit comment 0 to remove the misstatement.