Closed
Bug 1344821
Opened 7 years ago
Closed 7 years ago
Intermittent browser_dbg-sourcemaps-bogus.js,browser_dbg-sourcemaps.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. -
Categories
(DevTools :: Debugger, defect, P2)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: intermittent-bug-filer, Assigned: jlast)
References
Details
(Keywords: intermittent-failure, Whiteboard: [stockwell unknown])
Filed by: wkocher [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=81816956&repo=mozilla-inbound https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-inbound-macosx64-debug/mozilla-inbound_yosemite_r7-debug_test-mochitest-e10s-devtools-chrome-1-bm136-tests1-macosx-build87.txt.gz
Blocks: 1344294
Summary: Intermittent devtools/client/debugger/new/test/mochitest/browser_dbg-sourcemaps-bogus.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. - → Intermittent browser_dbg-sourcemaps-bogus.js,browser_dbg-sourcemaps.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. -
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jlaster
Priority: -- → P2
Comment hidden (Intermittent Failures Robot) |
Comment 2•7 years ago
|
||
This failure almost always occurs on osx debug e10s. Failures appear to have started with the update to tests in bug 1344294. These are NOT normally long-running tests on this platform: https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-central-macosx64-debug/mozilla-central_yosemite_r7-debug_test-mochitest-e10s-devtools-chrome-1-bm107-tests1-macosx-build22.txt.gz TEST-OK | devtools/client/debugger/new/test/mochitest/browser_dbg-sourcemaps-bogus.js | took 6930ms TEST-OK | devtools/client/debugger/new/test/mochitest/browser_dbg-sourcemaps.js | took 15686ms Failure screenshots show the browser with one new tab and the spinner. Failure logs typically end like: ... 10:40:40 INFO - Console message: [JavaScript Warning: "Expected end of value but found ‘!’. Error in parsing value for ‘margin-inline-start’. Declaration dropped." {file: "chrome://devtools/content/debugger/new/index.html" line: 0 column: 8 source: "-1000px !important"}] 10:40:40 INFO - Removing tab. 10:40:40 INFO - Waiting for event: 'TabClose' on [object XULElement]. 10:40:40 INFO - Got event: 'TabClose' on [object XULElement]. 10:40:40 INFO - Tab removed and finished closing 10:40:40 INFO - Buffered messages finished 10:40:40 INFO - TEST-UNEXPECTED-FAIL | devtools/client/debugger/new/test/mochitest/browser_dbg-sourcemaps.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. - 10:40:40 INFO - MEMORY STAT | vsize 4917MB | residentFast 1057MB | heapAllocated 226MB 10:40:40 INFO - TEST-OK | devtools/client/debugger/new/test/mochitest/browser_dbg-sourcemaps.js | took 102509ms
Comment 3•7 years ago
|
||
thanks for working on this :jlast, if you need more info on the failure rates or patterns, I am happy to help.
Whiteboard: [stockwell needswork]
Assignee | ||
Comment 4•7 years ago
|
||
Thanks :jmaher, i'm fairly new to intermittents and this is an interesting one too. Some questions I have are: * what's the frequency, are there platforms that are more common. * is it mostly / exclusively debug mode? * are there differences between the devtools/client/debugger/new intermittents or are they equally likely and un-correlated Also, if you could give me a set of bad try runs i could use that to search through the logs.
Comment 5•7 years ago
|
||
these are almost all on osx debug e10s tests, a few instances of win8/linux64 debug e10s as well. I am not sure if this is related to any other devtools/client/debugger/new intermittents, but looking there are 23 of them: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=devtools%2Fclient%2Fdebugger%2Fnew&list_id=13482647 I do wonder if this is a simple fix to clean them all up as they seem to be osx debug related- they all started around the same time. Here is a way to look at all the failures we have found for a given bug: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1344821&startday=2017-03-01&endday=2017-03-10&tree=all this started here: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&filter-searchStr=osx%20debug%20devtools&tochange=1f2df690050b0a553ae716f273d15fb2b6d45334&fromchange=a1535bb7d31397edde81076bd137d344593dcd9f&selectedJob=81720769 either bug 1344563, bug 1331342, bug 1341994, or bug 1344294. Possibly bisect it down if reading the source doesn't help much?
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 10•7 years ago
|
||
something greatly reduced the frequency here! pulling it off my radar for now.
Whiteboard: [stockwell needswork] → [stockwell unknown]
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 15•7 years ago
|
||
Fixing as the rate is pretty low
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Comment hidden (Intermittent Failures Robot) |
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•