Intermittent devtools/client/memory/test/browser/browser_memory_allocationStackDisplay_01.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. -

RESOLVED FIXED

Status

()

Firefox
Developer Tools: Memory
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Treeherder Bug Filer, Assigned: fitzgen)

Tracking

(Blocks: 1 bug, {intermittent-failure})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Component: Developer Tools → Developer Tools: Memory
Blocks: 1221517
Looks like this is timing out right as it is finishing. Both TEST-UNEXPECTED-FAIL from the timeout and TEST-OK happen at 16:49:06. What is the default timeout these days? 70-80s?

> 16:49:06     INFO -  267 INFO Closing memory panel.
> 16:49:06     INFO -  268 INFO Console message: [JavaScript Warning: "Error in parsing value for ‘height’.  Declaration dropped." {file: "chrome://devtools/content/memory/memory.xhtml" line: 0 column: 26 source: "padding:0;margin:0;height:-234px;"}]
> 16:49:06     INFO -  269 INFO Console message: [JavaScript Warning: "Error in parsing value for ‘height’.  Declaration dropped." {file: "chrome://devtools/content/memory/memory.xhtml" line: 0 column: 0 source: "-198px"}]
> 16:49:06     INFO -  270 INFO Closed memory panel successfully.
> 16:49:06     INFO -  271 INFO Removing tab.
> 16:49:06     INFO -  272 INFO Waiting for event: 'TabClose' on [object XULElement].
> 16:49:06     INFO -  273 INFO Got event: 'TabClose' on [object XULElement].
> 16:49:06     INFO -  274 INFO Tab removed and finished closing
> 16:49:06     INFO -  275 INFO TEST-UNEXPECTED-FAIL | devtools/client/memory/test/browser/browser_memory_allocationStackDisplay_01.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. -
> 16:49:06     INFO -  MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
> 16:49:06     INFO -  MEMORY STAT | vsize 1172MB | residentFast 282MB | heapAllocated 117MB
> 16:49:06     INFO -  276 INFO TEST-OK | devtools/client/memory/test/browser/browser_memory_allocationStackDisplay_01.js | took 79904ms
Oh, but that can be overridden: https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#1638 so looks like maybe 60 seconds: https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#1532.  And maybe setup / teardown is included in the time reported here (just guessing)
Assignee: nobody → nfitzgerald
Status: NEW → ASSIGNED
Created attachment 8778385 [details] [diff] [review]
memory-panel-intermittents.patch
Attachment #8778385 - Flags: review?(jimb)

Updated

2 years ago
Attachment #8778385 - Flags: review?(jimb) → review+
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/5d16dca06481
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Keywords: checkin-needed
You need to log in before you can comment on or make changes to this bug.