Closed Bug 1087886 Opened 10 years ago Closed 7 years ago

Intermittent 84400-1.html | image comparison (==), max difference: 1, number of differing pixels: 1

Categories

(Core :: Layout, defect, P3)

x86
Gonk (Firefox OS)
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox52 --- unaffected
firefox53 --- unaffected
firefox54 --- fixed

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell fixed])

b2g_emulator_vm mozilla-inbound opt test reftest-4

https://treeherder.mozilla.org/ui/logviewer.html#?job_id=3233095&repo=mozilla-inbound

17:51:23 INFO - REFTEST TEST-UNEXPECTED-FAIL | http://10.0.2.2:8888/tests/layout/reftests/bugs/84400-1.html | image comparison (==), max difference: 1, number of differing pixels: 1
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
(In reply to OrangeFactor Robot from comment #63)
> 36 failures in 836 pushes (0.043 failures/push) were associated with this
> bug in the last 7 days.  
> 
> ** This failure happened more than 30 times this week! Resolving this bug is
> a high priority. **
> 
> ** Try to resolve this bug as soon as possible. If unresolved for 2 weeks,
> the affected test(s) may be disabled. **
> 
> Repository breakdown:
> * mozilla-inbound: 33
> * mozilla-central: 1
> * mozilla-aurora: 1
> * autoland: 1
> 
> Platform breakdown:
> * android-4-3-armv7-api15: 36
> 
> For more details, see:
> https://brasstacks.mozilla.com/orangefactor/
> ?display=Bug&bugid=1087886&startday=2017-02-06&endday=2017-02-12&tree=all

This most recent batch of failures is fallout from bug 1315570 landing, and I just filed bug 1339239 to track it since the failure isn't exactly the same.
:jet, can we get someone to look at this issue, we had 81 failures yeterday alone, I would find it hard to imagine this is not fixable with almost 80% failure rate on android.  Possibly this test could be disabled on android if it doesn't have a lot of value there, open to options.
Flags: needinfo?(bugs)
Let's see how this looks after the test fix in bug 1339239 lands.
Flags: needinfo?(bugs)
this looks fixed!
Status: REOPENED → RESOLVED
Closed: 9 years ago7 years ago
Resolution: --- → FIXED
Whiteboard: [stockwell fixed]
You need to log in before you can comment on or make changes to this bug.