Closed Bug 586900 Opened 9 years ago Closed 9 years ago

ERROR TEST-UNEXPECTED-FAIL | /tests/layout/base/tests/test_bug569520.html | Second listener should fire after first listener

Categories

(Core :: Layout, defect)

defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: mwu, Assigned: bzbarsky)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1281679476.1281682738.1925.gz

s: talos-r3-fed-040
747 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/base/tests/test_bug569520.html | Second listener should fire after first listener
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
I'll look into this when I get back, but that's _very_ odd behavior....  Basically means JS_Now returned the same time 20ms apart.
philringnalda%gmail.com
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1281933019.1281936296.30475.gz
Rev3 Fedora 12 mozilla-central debug test mochitests-4/5 on 2010/08/15 21:30:19

s: talos-r3-fed-003
747 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/base/tests/test_bug569520.html | Second listener should fire after first listener
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
philringnalda%gmail.com
http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1282266590.1282269875.12055.gz
Rev3 Fedora 12 tracemonkey debug test mochitests-4/5 on 2010/08/19 18:09:50

s: talos-r3-fed-033
747 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/base/tests/test_bug569520.html | Second listener should fire after first listener
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
PROCESS-CRASH | Main app process exited normally | application crashed (minidump found)
Thread 0 (crashed)
I pushed http://hg.mozilla.org/mozilla-central/rev/a758e294ed9e to effectively disable this part of the test (switched to a >= test).  The reason it was failing is that the timer thread delay line filter was causing the refresh driver timer to fire in 0ms (or more precisely somewhere around 100us) instead of 20ms:

-1602586848[c0a5e0]: [this=22c25340] time between PostTimerEvent() and Fire(): 0.000000ms
-1602586848[c0a5e0]: [this=22bc95f0] expected delay time   20ms
-1602586848[c0a5e0]: [this=22bc95f0] actual delay time   0.000000ms
-1602586848[c0a5e0]: [this=22bc95f0] (mType is 1)       -------
-1602586848[c0a5e0]: [this=22bc95f0]     delta            -20ms
-1602586848[c0a5e0]: UpdateFilter: smoothSlack = -15.2812, filterLength = 32

Note that smoothSlack value; that's effectively giving all timer delays a -22ms adjustment.

I filed bug 590422 on trying to fix xpcom timers.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Assignee: nobody → bzbarsky
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.