Closed Bug 1018502 Opened 11 years ago Closed 10 years ago

Intermittent test_transitions_events.html | unexpected event on SPAN element with id {'six','five'} elapsedTime=0.5 propertyName='color'

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: KWierso, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=40766090&tree=Mozilla-Inbound Android 4.0 Panda mozilla-inbound debug test mochitest-8 on 2014-05-30 15:25:14 PDT for push 9ae055051998 slave: panda-0245 15:38:39 INFO - 1042 INFO TEST-START | /tests/layout/style/test/test_transitions_events.html 15:38:39 INFO - 1043 INFO TEST-INFO | dumping last 15 message(s) 15:38:39 INFO - 1044 INFO TEST-INFO | if you need more context, please use SimpleTest.requestCompleteLog() in your test 15:38:39 INFO - 1045 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1046 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1047 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1048 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1049 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1050 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1051 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | transitionend on body on root 15:38:39 INFO - 1052 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | propertyName for transitionend on body 15:38:39 INFO - 1053 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | elapsedTime for transitionend on body 15:38:39 INFO - 1054 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1055 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1056 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1057 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1058 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1059 INFO TEST-PASS | /tests/layout/style/test/test_transitions_events.html | undefined 15:38:39 INFO - 1060 INFO TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_transitions_events.html | unexpected event on SPAN element with id 'six' elapsedTime=0.5 propertyName='color' 15:38:39 INFO - 1061 INFO TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_transitions_events.html | unexpected event on SPAN element with id 'five' elapsedTime=0.5 propertyName='color' 15:39:39 INFO - 1062 INFO TEST-INFO | MEMORY STAT vsize after test: 868896768 15:39:39 INFO - 1063 INFO TEST-INFO | MEMORY STAT residentFast after test: 259231744 15:39:39 INFO - 1064 INFO TEST-INFO | MEMORY STAT heapAllocated after test: 36346832 15:39:39 INFO - 1065 INFO TEST-END | /tests/layout/style/test/test_transitions_events.html | finished in 9005ms
Could this be related to your recent changes?
Flags: needinfo?(birtles)
Based on the timing, it seems highly likely I'm to blame, yet I didn't touch anything to do with *transition* events. I will try to reproduce.
Flags: needinfo?(birtles)
As far as I can tell, this has only happened once and on Android. Comparing the log in comment 0 with the test, this failure is consistent with the setTimeout callback not running until after the transition (duration: 30s) has complete. It may be something in my code changes has altered the timing making this more likely to occur but from quickly skimming through my recent changes nothing jumps out yet. I'd like to leave this open and see if it happens again. If it does, it might shed more light on what is happening. It may be that we simply need to change the transition duration to something > 30s. For SMIL tests we often use 100s or so due to build machines getting really bogged down.
(In reply to Brian Birtles (:birtles) from comment #3) > As far as I can tell, this has only happened once and on Android. Comparing > the log in comment 0 with the test, this failure is consistent with the > setTimeout callback not running until after the transition (duration: 30s) > has complete. I misread the test, it's actually duration 500ms in this case. So trying to understand what's happening: 1. We trigger the transition of 500ms 2. We call setTimeout with a delay of 100ms 3. We run the setTimeout callback within 500ms and notice that the transition hasn't stopped yet so we set did_stops to true and trigger the changes that should cause the transition to stop when computed style is updated 4. We tick the refresh driver and queue the transition end event, but we do this before computing style and noticing the transition has finished <-- Is this even possible? 5. We get the transition end event and notice did_stops is true so we fail. I'm not really sure if 4 is possible. If my changes are to blame, it may be because I've somehow changed the handling of sentinel values.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
(In reply to Treeherder Robot from comment #67) Spun off to bug 1156451.
You need to log in before you can comment on or make changes to this bug.