Intermittent TEST-UNEXPECTED-TIMEOUT | /offscreen-canvas/pixel-manipulation/2d.imageData.put.dirty.outside.worker.html | expected OK after Assertion failure: firstTimeStamp == mTimers[0]->Timeout(), at TimerThread.cpp:661

RESOLVED INCOMPLETE

Status

()

Core
Canvas: 2D
P3
normal
RESOLVED INCOMPLETE
a year ago
10 months ago

People

(Reporter: Treeherder Bug Filer, Unassigned)

Tracking

({bulk-close-intermittents, intermittent-failure})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: gfx-noted)

Olli, do you think maybe we should just remove this assertion?  The code clearly works on platforms where TimeStamp is stable.
Flags: needinfo?(bugs)
I guess so. It is still worrisome that we don't have reliable timestamps on Windows.
We rely on timestamps comparisons everywhere, and all the time even more.
Flags: needinfo?(bugs)
We do (should have) after bug 1345939, fixed a month ago.  But it could be that the VM still doesn't provide it in a stable way and we have no way to detect this, relying on the windows API to cover for us.

I would be really interested in what the timestamps in test values are when this assertion fails.

Comment 4

a year ago
1 failures in 720 pushes (0.001 failures/push) were associated with this bug in the last 7 days.   

Repository breakdown:
* autoland: 1

Platform breakdown:
* windows7-32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1380518&startday=2017-07-10&endday=2017-07-16&tree=all
Whiteboard: gfx-noted
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.