Closed
Bug 1065355
Opened 11 years ago
Closed 11 years ago
Make timeline and shadereditor tests run on e10s
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(e10s+)
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: vporof, Assigned: markh)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
12.01 KB,
patch
|
pbro
:
review+
|
Details | Diff | Splinter Review |
37.93 KB,
patch
|
pbro
:
review+
|
Details | Diff | Splinter Review |
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: target.window is null
Full stack: initFrontend@chrome://mochitests/content/browser/browser/devtools/timeline/test/head.js:76:7
Tester_execTest@chrome://mochikit/content/browser-test.js:659:9
Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:556:7
Updated•11 years ago
|
Assignee: nobody → mhammond
tracking-e10s:
--- → +
Updated•11 years ago
|
Blocks: e10s-tests
Assignee | ||
Comment 1•11 years ago
|
||
The patch in bug 1067229 plus this attachment gets the timeline tests passing when run under e10s. Victor, what is the "right" thing to do re the debuggee here?
Attachment #8489224 -
Flags: feedback?(vporof)
Assignee | ||
Comment 2•11 years ago
|
||
FTR, the 'shadereditor' tests have an almost identical problem - head.js tries to get a 'debuggee' object in a couple of places but it seems unused by the tests.
Assignee | ||
Comment 3•11 years ago
|
||
Same basic fix for both timeline and shadereditor, so we might as well kill both birds here.
Status: NEW → ASSIGNED
Points: --- → 3
Flags: qe-verify-
Flags: firefox-backlog+
Summary: Make timeline tests run on e10s → Make timeline and shadereditor tests run on e10s
Assignee | ||
Comment 4•11 years ago
|
||
As we discussed on IRC, I've just dropped the "debuggee" result from initShaderEditor() - however, I also changed it to return an object instead of an array so it is easier to add a debuggee back in the future without touching the tests that don't need it.
This gets all timeline tests passing for me locally.
Attachment #8489224 -
Attachment is obsolete: true
Attachment #8489224 -
Flags: feedback?(vporof)
Attachment #8491955 -
Flags: review?(pbrosset)
Assignee | ||
Comment 5•11 years ago
|
||
An almost identical patch, but for the shadereditor.
Attachment #8491956 -
Flags: review?(pbrosset)
Updated•11 years ago
|
Iteration: --- → 35.2
Updated•11 years ago
|
Attachment #8491955 -
Flags: review?(pbrosset) → review+
Updated•11 years ago
|
Attachment #8491956 -
Flags: review?(pbrosset) → review+
Assignee | ||
Comment 6•11 years ago
|
||
Comment 7•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/d4e8b9359261
https://hg.mozilla.org/mozilla-central/rev/0ea262e00917
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35
Comment 8•10 years ago
|
||
Sorry for the spam. Moving bugs to Firefox :: Developer Tools: Performance Tools (Profiler/Timeline).
dkl
Component: Developer Tools: Timeline → Developer Tools: Performance Tools (Profiler/Timeline)
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•