Closed Bug 1554342 Opened 5 years ago Closed 5 years ago

Categories

(Core :: CSS Parsing and Computation, defect, P5)

defect

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- unaffected
firefox68 --- unaffected
firefox69 --- disabled
firefox70 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: dholbert)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure, regression)

Attachments

(1 file)

Summary: Intermittent /css/css-contain/contain-layout-baseline-005.html | Testing http://web-platform.test:8000/css/css-contain/contain-layout-baseline-005.html == http://web-platform.test:8000/css/css-contain/reference/contain-layout-baseline-005-ref.html → Perma [tier 2] /css/css-contain/contain-layout-baseline-005.html | Testing http://web-platform.test:8000/css/css-contain/contain-layout-baseline-005.html == http://web-platform.test:8000/css/css-contain/reference/contain-layout-baseline-005-ref.html

This looks basically like a form of bug 1480862. (2 fuzzy pixels at the corner of a native widget -- a <select> dropdown button in this case)

We should annotate this test as having 2 pixels fuzzy, rather than annotating it as failing as we currently have done.

Flags: needinfo?(dholbert)

Right now it's annotated as failing on android, which is why we haven't been getting reports recently. But, per comment 9, we should just annotate it as fuzzy instead.

Assignee: nobody → dholbert
Status: NEW → ASSIGNED
Flags: needinfo?(dholbert)

So in an x86_64 emulator log as well as an x86 emulator log (both from before we annotated this test as failing), I see the following for this test failure:

  INFO    Found 2 pixels different, maximum difference per channel 9

I'll just use those numbers in the annotation. For now, I'll expect precisely that much to differ, so we can tell if the issue goes away. (This is a reliable failure, given that we've annotated this test as reliably failing right now without incurring "unexpected-pass" oranges yet as far as I'm aware. And it seems likely that we're always failing in that same way.)

This test reliably fails (at least, it's currently annotated as such), but the
failure appears to always only have 2px differing with maximum color-channel
difference of 9. This patch tightens the annotation to express precisely that
expectation.

Try run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=923269a38517e23453e8e51f1982b9fe6e107512

(Try run is only exercising the x86_64 android emulator, but that should be sufficient. I couldn't figure out how to get ./mach try fuzzy to offer me x86 android emulator web-platform-test-runs)

Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/3dfc7260f081
Annotate web-platform-test contain-layout-baseline-005.html as fuzzy rather than failing. (no review, just adjusting a test-annotation)
Blocks: 1563334
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: