Sounds like maybe we just need to remove or update the fuzzy annotation, to annotate the test as passing (or sometimes-passing, if it's not 100%) on this platform? The test is annotated as `fuzzy-if(appleSilicon,255-255,167058-167058)` which essentially means "Expected to catastrophically fail" (expecting 167,058 pixels to differ). That annotation was added as part of bug 1706716, which was a broad "annotate all the existing failures on this platform, to reflect reality" sort of patch. Probably those mismatching pixels were just all of the video areas failing to render at all, and probably that was fixed (partly or entirely) by bug 1792257?
Bug 1796590 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sounds like maybe we just need to remove or update the fuzzy annotation, to annotate the test as passing (or sometimes-passing, if it's not 100%) on this platform? The test is currently annotated as `fuzzy-if(appleSilicon,255-255,167058-167058)` which essentially means "Expected to catastrophically fail" (expecting 167,058 pixels to always differ between testcase & reference case). That annotation was added as part of bug 1706716, which was a broad "annotate all the existing failures on this platform, to reflect reality" sort of patch. Probably those mismatching pixels were just all of the video areas failing to render at all, and probably that was fixed (partly or entirely) by bug 1792257?
Sounds like maybe we just need to remove or update the fuzzy annotation, to reflect the fact that this test is always passing (or sometimes-passing, if it's not 100%) on this platform? [EDIT: Looks like this is indeed always-passing, per the bug title and the perma-orange on recent history at https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=macosx11%2Cr6 .) The test is currently annotated as `fuzzy-if(appleSilicon,255-255,167058-167058)` which essentially means "Expected to catastrophically fail" (expecting 167,058 pixels to always differ between testcase & reference case). That annotation was added as part of bug 1706716, which was a broad "annotate all the existing failures on this platform, to reflect reality" sort of patch. Probably those mismatching pixels were just all of the video areas failing to render at all, and probably that was fixed (partly or entirely) by bug 1792257?
Sounds like maybe we just need to remove or update the fuzzy annotation, to reflect the fact that this test is always passing (or sometimes-passing, if it's not 100%) on this platform? [EDIT: Looks like this is indeed always-passing, per the bug title and the perma-orange on recent history at https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=macosx11%2Cr6 .] The test is currently annotated as `fuzzy-if(appleSilicon,255-255,167058-167058)` which essentially means "Expected to catastrophically fail" (expecting 167,058 pixels to always differ between testcase & reference case). That annotation was added as part of bug 1706716, which was a broad "annotate all the existing failures on this platform, to reflect reality" sort of patch. Probably those mismatching pixels were just all of the video areas failing to render at all, and probably that was fixed (partly or entirely) by bug 1792257?