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-compare](https://hg-edge.mozilla.org/mozilla-central/raw-file/default/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EhLYfspuSdywbtFqX0GZHg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1) 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. (Note: bug 1982907 covers the other fuzzy failure there, and bug 1982914 covers the fatal assertion-failure (crash) in `text-context-fill.svg`.)
Bug 1982937 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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-compare](https://hg-edge.mozilla.org/mozilla-central/raw-file/default/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EhLYfspuSdywbtFqX0GZHg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1) 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`.)
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](https://hg-edge.mozilla.org/mozilla-central/raw-file/default/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EhLYfspuSdywbtFqX0GZHg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1) 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`.)
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](https://hg-edge.mozilla.org/mozilla-central/raw-file/default/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EhLYfspuSdywbtFqX0GZHg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1) 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`.)