Closed Bug 1064136 Opened 10 years ago Closed 8 years ago

Intermittent test_overdraw.html | Overdraw: 0 - expected PASS

Categories

(Core :: Graphics, defect, P3)

defect

Tracking

()

RESOLVED INVALID
mozilla35
Tracking Status
firefox33 --- unaffected
firefox34 --- unaffected
firefox35 --- fixed
firefox-esr31 --- unaffected

People

(Reporter: philor, Unassigned)

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=47578898&tree=Mozilla-Inbound
Windows 7 32-bit mozilla-inbound opt test mochitest-4 on 2014-09-07 20:17:12 PDT for push f73f0c65c4cb
slave: t-w732-ix-076

20:23:34     INFO -  737 INFO TEST-START | /tests/gfx/tests/mochitest/test_overdraw.html
20:23:35     INFO -  738 INFO TEST-UNEXPECTED-FAIL | /tests/gfx/tests/mochitest/test_overdraw.html | Overdraw: 0 - expected PASS
20:23:35     INFO -  739 INFO TEST-OK | /tests/gfx/tests/mochitest/test_overdraw.html | took 45ms
BenWa, this is happening pretty frequently. We need a fix or backout ASAP.
Flags: needinfo?(bgirard)
I'm going to disable the test. It needs to be adjusted.
Assignee: nobody → bgirard
Flags: needinfo?(bgirard)
https://hg.mozilla.org/mozilla-central/rev/004e55591499
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
The comment in the manifest is pointing at this bug as the one that needs fixing before the test can be re-enabled, which doesn't seem right. Is there a follow-up bug filed somewhere for getting this fixed and re-enabled or should this bug be reopened?
Flags: needinfo?(bgirard)
I just meant that we should fix this intermittent failure before we re-enable this bug.
Flags: needinfo?(bgirard)
This bug was closed. We should either reopen it then or file a new bug for fixing and re-enabling.
Ok, let's re-open this one since it has the information.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Assignee: bgirard → nobody
Status: REOPENED → RESOLVED
Closed: 10 years ago8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.