Closed Bug 1439846 Opened 6 years ago Closed 6 years ago

Intermittent devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N)

Categories

(DevTools :: Inspector, defect, P5)

defect

Tracking

(firefox60 fixed)

RESOLVED FIXED
Firefox 60
Tracking Status
firefox60 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: daisuke)

References

Details

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

Attachments

(1 file)

Filed by: csabou [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=163290839&repo=mozilla-central

https://queue.taskcluster.net/v1/task/eIoVnqyQQAaNjiORXZv_BA/runs/1/artifacts/public/logs/live_backing.log

21:00:47     INFO -  37 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be visibled -
21:00:47     INFO -  38 INFO Checking animation detail visibility when choose node which has animations
21:00:47     INFO -  39 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  40 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  41 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  42 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  43 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  44 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  45 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  46 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  47 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  48 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  49 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  50 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  51 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  52 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  53 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  54 INFO Console message: [JavaScript Warning: "Removed unsafe attribute. Element: svg. Attribute: xmlns." {file: "resource://devtools/shared/base-loader.js -> resource://devtools/client/shared/vendor/react-dom-dev.js" line: 13001}]
21:00:47     INFO -  Buffered messages logged at 21:00:01
21:00:47     INFO -  55 INFO Selecting the node for '[Front for domnode/server1.conn4.child1/domnode32]'
21:00:47     INFO -  Buffered messages logged at 21:00:37
21:00:47     INFO -  56 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be unvisibled after choose html node -
21:00:47     INFO -  57 INFO Checking animation detail visibility when choose node which has an animation
21:00:47     INFO -  Buffered messages logged at 21:00:39
21:00:47     INFO -  58 INFO Selecting the node for '[Front for domnode/server1.conn4.child1/domnode37]'
21:00:47     INFO -  Buffered messages logged at 21:00:43
21:00:47     INFO -  59 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be visibled after choose .cssanimation-normal node -
21:00:47     INFO -  60 INFO Leaving test bound
21:00:47     INFO -  Buffered messages logged at 21:00:47
21:00:47     INFO -  61 INFO Removing tab.
21:00:47     INFO -  62 INFO Waiting for event: 'TabClose' on [object XULElement].
21:00:47     INFO -  63 INFO Got event: 'TabClose' on [object XULElement].
21:00:47     INFO -  64 INFO Tab removed and finished closing
21:00:47     INFO -  Buffered messages finished
21:00:47    ERROR -  65 INFO TEST-UNEXPECTED-FAIL | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
21:00:47     INFO -  GECKO(2844) | MEMORY STAT | vsize 2347MB | vsizeMaxContiguous 130543455MB | residentFast 420MB | heapAllocated 108MB
It seems to me the test is slow in the first place.

From a failure log;

TEST-INFO | screenshot: exit 0
Buffered messages logged at 07:12:03
15 INFO Entering test bound
16 INFO Adding a new tab with URL: http://example.com/browser/devtools/client/inspector/animation/test/doc_multi_timings.html
Buffered messages logged at 07:12:04
17 INFO Tab added and finished loading
18 INFO Loading the helper frame script chrome://mochitests/content/browser/devtools/client/inspector/animation/test/doc_frame_script.js
19 INFO Loading the helper frame script chrome://devtools/content/shared/frame-script-utils.js
20 INFO Opening the inspector
21 INFO Opening the toolbox
Buffered messages logged at 07:12:06
Buffered messages logged at 07:12:21
24 INFO Toolbox opened and focused
Buffered messages logged at 07:12:22
25 INFO Selecting the newanimationinspector sidebar
Buffered messages logged at 07:12:26
34 INFO Checking animation detail visibility if animation was unselected
35 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | The detail pane should be in the DOM -
36 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be unvisibled -
37 INFO Checking animation detail visibility if animation was selected by click
38 INFO Click on animation 0 in the timeline
Buffered messages logged at 07:12:52
39 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be visibled -
40 INFO Checking animation detail visibility when choose node which has animations
Buffered messages logged at 07:12:53
55 INFO Selecting the node for '[Front for domnode/server1.conn4.child1/domnode32]'
Buffered messages logged at 07:13:31
56 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be unvisibled after choose html node -
57 INFO Checking animation detail visibility when choose node which has an animation
Buffered messages logged at 07:13:33
58 INFO Selecting the node for '[Front for domnode/server1.conn4.child1/domnode37]'
Buffered messages logged at 07:13:38
59 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js | detailEl should be visibled after choose .cssanimation-normal node -
60 INFO Leaving test bound
Buffered messages logged at 07:13:40
61 INFO Removing tab.
62 INFO Waiting for event: 'TabClose' on [object XULElement].
63 INFO Got event: 'TabClose' on [object XULElement].
64 INFO Tab removed and finished closing
Buffered messages finished
65 INFO TEST-UNEXPECTED-FAIL |

It took approximately 40s between 'Checking animation detail visibility when choose node which has animations' and "Selecting the node for '[Front for domnode/server1.conn4.child1/domnode32]'".  So I guess "await selectNodeAndWaitForAnimations(htmlNode, inspector);" [1] is something broken inside it.  I believe Daisuke knows something.
 
I can also see browser_animation_keyframes-graph_computed-value-path.js causes timeout as well. 

[1] https://hg.mozilla.org/mozilla-central/file/dd6caba14142/devtools/client/inspector/animation/test/browser_animation_animation-detail_visibility.js#l24
[2] https://treeherder.mozilla.org/logviewer.html#?job_id=163284605&repo=mozilla-central&lineNumber=2944
Flags: needinfo?(hikezoe) → needinfo?(dakatsuka)
Thanks, I'll take a look.
See Also: → 1440831
Umm, I tried with debug print at last week, could not reproduce,,
* https://treeherder.mozilla.org/#/jobs?repo=try&revision=3ba8610a04bdd468f36f7400e6e5d1428c7fc1aa
* https://treeherder.mozilla.org/#/jobs?repo=try&revision=0acdfd21824df899b4479ee72f11dd4b5f133537

However, it is taking too long time for windows10-64-ccov debug in above try, anyway.
* windows10-64-ccov debug: about 8 ~ 9sec
* Windows 10 x64 debug: about 1.5sec

Please let me think to reduce the time again.
If we introduce bug 1438755, though actually the time of graphs rendering reduce to about 2/3, it could not be a fundamental resolving. Of course, the graph rendering is one of reasons, but opening the inspector (even without graph) as well is taking a long time.
So, please let me add requestLongerTimeout at this time. 
(The test for previous animation inspector as well is calling requestLongerTimeout.)

Thanks.
Flags: needinfo?(dakatsuka)
I am wondering DAMP includes animation inspector as well?

http://docs.firefox-dev.tools/tests/performance-tests.html
Oh, thanks Hiro, let me try!
Comment on attachment 8955026 [details]
Bug 1439846: Add requestLongerTimeout to browser_animation_animation-detail_visibility.

https://reviewboard.mozilla.org/r/224202/#review230370
Attachment #8955026 - Flags: review?(gl) → review+
Comment on attachment 8955026 [details]
Bug 1439846: Add requestLongerTimeout to browser_animation_animation-detail_visibility.

https://reviewboard.mozilla.org/r/224202/#review230372

::: commit-message-52975:1
(Diff revision 1)
> +Bug 1439846: Add requestLongerTimeout to this test. r?gl

Add requestLongerTimeout to browser_animation_animation-detail_visibility.
Whiteboard: [stockwell needswork]
I'm sorry for delay.

I have tried DAMP test[1]. This is the result[2].
The time for inspector.animationinspector.open and inspector.oldanimation.open is that opened a html which includes 22 animations, then opened the inspector, then selected the animation inspector.

The results are:
inspector.animationinspector.open: 769.33 ± 0.61%
inspector.oldanimationinspector.open: 905.00 ± 0.51% 

The new animation inspector did not so slow against previous one.

So, how we should address this bug.
I think we can choice two ways.

1. Add requestLongerTimeout.
2. Disable this test for windows10-64-ccov since a debugger test have disabled for windows10-64-ccov recently with same reason in bug 1424154.
Gabriel, how do you think?

[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=b12d6ee626bd23a93750c47f711c97c94978f120&selectedJob=166408346
[2] https://treeherder.mozilla.org/perf.html#/comparesubtest?originalProject=mozilla-central&newProject=try&newRevision=b12d6ee626bd23a93750c47f711c97c94978f120&originalSignature=f79b6a4f1f8f53326d3056f6c8008c0ff4de0a94&newSignature=f79b6a4f1f8f53326d3056f6c8008c0ff4de0a94&framework=1&selectedTimeRange=172800
Flags: needinfo?(gl)
Yes #1 sounds fine and that's what we have reviewed already.
Flags: needinfo?(gl)
Okay, thanks.
I'll land it.
Assignee: nobody → dakatsuka
Pushed by dakatsuka@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d55b703721d2
Add requestLongerTimeout to browser_animation_animation-detail_visibility. r=gl
https://hg.mozilla.org/mozilla-central/rev/d55b703721d2
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
Whiteboard: [stockwell needswork] → [stockwell fixed:other]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: