Closed
Bug 1473586
Opened 6 years ago
Closed 6 years ago
Intermittent devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | This test exceeded the timeout threshold. It should be rewritten or split up.
Categories
(DevTools :: Inspector: Animations, defect, P5)
DevTools
Inspector: Animations
Tracking
(firefox63 fixed)
RESOLVED
FIXED
Firefox 63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: daisuke)
Details
(Keywords: intermittent-failure, Whiteboard: [TV-bf fail:fail][stockwell needswork])
Attachments
(1 file)
Filed by: aciure [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=186601740&repo=mozilla-central https://queue.taskcluster.net/v1/task/RVINKbkuSrG46fm9XVrwYQ/runs/1/artifacts/public/logs/live_backing.log 13:55:17 INFO - 501 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | The element should not have the compositor css class after rewinding - 13:55:17 INFO - 502 INFO Click on pause/resume button 13:55:17 INFO - Buffered messages logged at 13:54:26 13:55:17 INFO - 503 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | The element should have the compositor css class after resuming - 13:55:17 INFO - 504 INFO Check compositor sign after setting the current time 13:55:17 INFO - 505 INFO Click 70 on scrubber controller 13:55:17 INFO - Buffered messages logged at 13:54:46 13:55:17 INFO - 506 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | The element should not have the compositor css class after setting the current time - 13:55:17 INFO - 507 INFO Click on pause/resume button 13:55:17 INFO - Buffered messages logged at 13:55:03 13:55:17 INFO - 508 INFO TEST-PASS | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | The element should have the compositor css class after resuming - 13:55:17 INFO - 509 INFO Leaving test bound 13:55:17 INFO - Buffered messages logged at 13:55:17 13:55:17 INFO - 510 INFO Removing tab. 13:55:17 INFO - 511 INFO Waiting for event: 'TabClose' on [object XULElement]. 13:55:17 INFO - 512 INFO Got event: 'TabClose' on [object XULElement]. 13:55:17 INFO - 513 INFO Tab removed and finished closing 13:55:17 INFO - Buffered messages finished 13:55:17 ERROR - 514 INFO TEST-UNEXPECTED-FAIL | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.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. - 13:55:17 INFO - GECKO(4976) | MEMORY STAT | vsize 2596MB | vsizeMaxContiguous 131079109MB | residentFast 618MB | heapAllocated 238MB 13:55:17 INFO - 515 INFO TEST-OK | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | took 173812ms 13:55:17 INFO - GECKO(4976) | ++DOCSHELL 00000272B575F000 == 2 [pid = 5648] [id = {cf98637b-b94a-4146-9bb4-76fb31e42e82}] 13:55:17 INFO - GECKO(4976) | ++DOMWINDOW == 3 (00000272BBB2F600) [pid = 5648] [serial = 122] [outer = 0000000000000000] 13:55:17 INFO - GECKO(4976) | ++DOMWINDOW == 4 (00000272B9751400) [pid = 5648] [serial = 123] [outer = 00000272BBB2F600] 13:55:17 INFO - 516 INFO checking window state
Comment 1•6 years ago
|
||
this test failure reproduced on test-verify as well as the previous push: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=cov%20win%20verify&tochange=085cdfb90903d4985f0de1dc7786522d9fb45596&fromchange=1dad493abb2dc49890a5d6a23340afa0719efd96&selectedJob=186634123
Whiteboard: [TV-bf fail:fail]
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 6•6 years ago
|
||
There have been 46 failures in the last week: - linux64 /debug: 34 - windows10-64-ccov / debug: 6 - linux64-ccov / debug: 6 Recent log file and snippet with the failure: https://treeherder.mozilla.org/logviewer.html#?job_id=189435627&repo=autoland&lineNumber=54007 [task 2018-07-22T23:09:14.135Z] 23:09:14 INFO - TEST-PASS | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | The element should have the compositor css class after resuming - [task 2018-07-22T23:09:14.136Z] 23:09:14 INFO - Leaving test bound [task 2018-07-22T23:09:14.139Z] 23:09:14 INFO - Buffered messages logged at 23:09:13 [task 2018-07-22T23:09:14.140Z] 23:09:14 INFO - Removing tab. [task 2018-07-22T23:09:14.141Z] 23:09:14 INFO - Waiting for event: 'TabClose' on [object XULElement]. [task 2018-07-22T23:09:14.141Z] 23:09:14 INFO - Got event: 'TabClose' on [object XULElement]. [task 2018-07-22T23:09:14.143Z] 23:09:14 INFO - Tab removed and finished closing [task 2018-07-22T23:09:14.144Z] 23:09:14 INFO - Buffered messages finished [task 2018-07-22T23:09:14.145Z] 23:09:14 INFO - TEST-UNEXPECTED-FAIL | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.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. - [task 2018-07-22T23:09:14.146Z] 23:09:14 INFO - GECKO(1950) | MEMORY STAT | vsize 2340MB | residentFast 539MB | heapAllocated 206MB [task 2018-07-22T23:09:14.147Z] 23:09:14 INFO - TEST-OK | devtools/client/inspector/animation/test/browser_animation_summary-graph_compositor.js | took 102539ms [task 2018-07-22T23:09:14.150Z] 23:09:14 INFO - GECKO(1950) | ++DOCSHELL 0x7f9ff1c59800 == 2 [pid = 2077] [id = {863aee85-f8ae-464a-913a-872701c27cc2}] [task 2018-07-22T23:09:14.151Z] 23:09:14 INFO - GECKO(1950) | ++DOMWINDOW == 6 (0x7f9ff5ab7200) [pid = 2077] [serial = 122] [outer = (nil)] [task 2018-07-22T23:09:14.151Z] 23:09:14 INFO - GECKO(1950) | ++DOMWINDOW == 7 (0x7f9ff024e800) [pid = 2077] [serial = 123] [outer = 0x7f9ff5ab7200] [task 2018-07-22T23:09:14.152Z] 23:09:14 INFO - checking window state :jgraham, would you please have a look? Thank you.
Flags: needinfo?(james)
Whiteboard: [TV-bf fail:fail] → [TV-bf fail:fail][stockwell needswork]
Comment 7•6 years ago
|
||
I'm pretty sure that I'm not the right person to look at this. Maybe sole can redirect to someone on the devtools team?
Flags: needinfo?(james) → needinfo?(spenades)
Updated•6 years ago
|
Component: Inspector → Animation Inspector
Flags: needinfo?(dakatsuka)
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 10•6 years ago
|
||
Thanks, I'll take a look.
Comment hidden (mozreview-request) |
Assignee | ||
Comment 12•6 years ago
|
||
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b9ba68039b0683f96b51bdeca5d21f5a09acdf04 I have tried to reduce the testing time. It could reduce about 18% compare with previous way in my local environment. And, added requestLongerTimeout, just to be safe.
Assignee: nobody → dakatsuka
Flags: needinfo?(dakatsuka)
Comment 13•6 years ago
|
||
mozreview-review |
Comment on attachment 8994734 [details] Bug 1473586: Reduce testing time and add requestLongerTimeout. https://reviewboard.mozilla.org/r/259254/#review266244
Attachment #8994734 -
Flags: review?(gl) → review+
Assignee | ||
Comment 14•6 years ago
|
||
Thanks, Gabriel! Will make the patch to land if the try was green.
Comment 15•6 years ago
|
||
Pushed by dakatsuka@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a3f6db75bb07 Reduce testing time and add requestLongerTimeout. r=gl
Comment 16•6 years ago
|
||
Backed out for failing talos headless at ts_paint_heavy Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=a3f6db75bb07da37512f032485af29f99649dd67 Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=189980910&repo=autoland&lineNumber=797 Backout: https://hg.mozilla.org/integration/autoland/rev/9bce60d444985d38f4cd049870c5431cfeb87cfd
Flags: needinfo?(dakatsuka)
Assignee | ||
Comment 17•6 years ago
|
||
Hi Andreea, thank you the information. However, I don't think this failure was occurred by this patch, since the error message is below. ``` TEST-UNEXPECTED-ERROR | ts_paint_heavy | 404 Client Error: Not Found for url: https://queue.taskcluster.net/v1/task/XIvF6qscStuH1ZCEDabRhg/artifacts/public%2Ftoday-simple.tgz ``` Could you check again??
Flags: needinfo?(dakatsuka)
Comment 18•6 years ago
|
||
:daisuke sure, will take a closed look at it and get back to you.
Comment 19•6 years ago
|
||
This failed on the backout too, so it's not from here. I apologize for that. Can you reland it or should i? Again, sorry for the confusion.
Flags: needinfo?(dakatsuka)
Assignee | ||
Comment 20•6 years ago
|
||
Thank you for the checking! If possible, could you re-land, please?
Flags: needinfo?(dakatsuka) → needinfo?(apavel)
Comment 21•6 years ago
|
||
Pushed by apavel@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2876ce49557d Reduce testing time and add requestLongerTimeout. r=gl
Updated•6 years ago
|
Flags: needinfo?(apavel)
Updated•6 years ago
|
Flags: needinfo?(spenades)
Comment 22•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/2876ce49557d
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
Comment hidden (Intermittent Failures Robot) |
Comment 24•6 years ago
|
||
We are trying to build a tool to automatically classify intermittent failures, which would provide a starting point for fixing the bug, reducing the manual work for the developers. We are collecting some feedback on the results, to see if they’re good enough and where we need to improve. For this bug, the tool says that the intermittent failure is most likely a: Test Timeout: This includes test failures in which a single test case or the whole test suite timed out. This might be due to an unresponsive or slow target system (e.g. either the system that executes the tests or the os itself), a test suite which has grown too large causing intermittent-timeouts or a timeout threshold for a process, thread, function call which was set too small/too large. Once you’re done investigating and/or fixing the bug, could you tell me: - Did the tool correctly recognize the type of intermittent failure? - Did the information from the tool help your analysis, the bug fixing process, or anything in the process? (please also let us know how the tool was useful and/or what would improve the tool's usefulness for you)
Assignee | ||
Updated•6 years ago
|
Flags: needinfo?(dakatsuka)
You need to log in
before you can comment on or make changes to this bug.
Description
•