Closed
Bug 1090929
Opened 10 years ago
Closed 10 years ago
Enable the debugger tests for e10s
Categories
(DevTools :: Debugger, defect)
Tracking
(e10s+)
RESOLVED
FIXED
Firefox 36
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: ejpbruel, Assigned: ejpbruel)
References
Details
Attachments
(16 files)
No description provided.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8513445 -
Flags: review?(mratcliffe)
Updated•10 years ago
|
Attachment #8513445 -
Flags: review?(mratcliffe) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Whiteboard: [leave-open]
Comment 3•10 years ago
|
||
Flags: in-testsuite+
Assignee | ||
Comment 4•10 years ago
|
||
Attachment #8514142 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 5•10 years ago
|
||
Green try push for the blackboxing tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=ebe1cafbed90
Assignee | ||
Comment 6•10 years ago
|
||
Green try push for the break-on-dom tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=d51d315e091f
Assignee | ||
Comment 7•10 years ago
|
||
I just realized those try pushes are probably invalid because I didn't enable the e10s tests on try (I had a commit that does that, but didn't include it in the diff I used to push to try).
The blackboxing tests already landed, but I'm confident those won't cause any problems. I will redo the try push for the break-on-dom tests. If there are any problems with the blackboxing tests, they should show up in that try push as well.
Assignee | ||
Comment 8•10 years ago
|
||
Attachment #8514267 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 9•10 years ago
|
||
Attachment #8514350 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 10•10 years ago
|
||
Attachment #8514436 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 11•10 years ago
|
||
Attachment #8514444 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 12•10 years ago
|
||
Attachment #8514449 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 13•10 years ago
|
||
Attachment #8514468 -
Flags: review?(mratcliffe)
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
Attachment #8514142 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8514267 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8514350 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8514436 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8514444 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8514449 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8514468 -
Flags: review?(mratcliffe) → review+
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → ejpbruel
Assignee | ||
Comment 14•10 years ago
|
||
Green try run for the break-on-dom tests:
https://hg.mozilla.org/try/rev/ca60639afdd6
Assignee | ||
Comment 15•10 years ago
|
||
Green try run for the pretty-print tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=ca60639afdd6
Assignee | ||
Comment 16•10 years ago
|
||
Assignee | ||
Comment 17•10 years ago
|
||
Assignee | ||
Comment 18•10 years ago
|
||
Attachment #8518077 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 19•10 years ago
|
||
Attachment #8518078 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 20•10 years ago
|
||
Attachment #8518085 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 21•10 years ago
|
||
Attachment #8518087 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 22•10 years ago
|
||
Attachment #8518089 -
Flags: review?(mratcliffe)
Assignee | ||
Updated•10 years ago
|
Attachment #8518089 -
Attachment is patch: true
Attachment #8518089 -
Attachment mime type: text/x-patch → text/plain
Assignee | ||
Comment 23•10 years ago
|
||
Attachment #8518090 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 24•10 years ago
|
||
Attachment #8518091 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 25•10 years ago
|
||
Once these patches land, about 90% of the frontend tests for the debugger should work on opt builds with E10S enabled.
On debug builds, the frontend tests are still leaking memory. Because I suspect the underlying cause is the same for each test, I've opened up a separate bug for this (1094749).
Depends on: 1094749
Updated•10 years ago
|
Attachment #8518077 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8518078 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8518085 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8518087 -
Flags: review?(mratcliffe) → review+
Updated•10 years ago
|
Attachment #8518089 -
Flags: review?(mratcliffe) → review+
Comment 26•10 years ago
|
||
Comment on attachment 8518090 [details] [diff] [review]
Enable the stack tests
Review of attachment 8518090 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/devtools/debugger/test/browser.ini
@@ +412,2 @@
> [browser_dbg_stack-03.js]
> +skip-if = e10s # TODO
Maybe add a bug number here.
Attachment #8518090 -
Flags: review?(mratcliffe) → review+
Comment 27•10 years ago
|
||
Comment on attachment 8518091 [details] [diff] [review]
Enable the remaining tests
Review of attachment 8518091 [details] [diff] [review]:
-----------------------------------------------------------------
gTab is sometimes not cleaned up, r+ if you fix it.
The TODO comments should probably have a bug number or explaination.
::: browser/devtools/debugger/test/browser_dbg_event-listeners-01.js
@@ +23,5 @@
> "Root actor should identify itself as a browser.");
>
> addTab(TAB_URL)
> + .then((aTab) => {
> + gTab = aTab;
gTab is not cleaned up anywhere... not sure why this doesn't leak but it should be cleaned up anyhow.
::: browser/devtools/debugger/test/browser_dbg_event-listeners-02.js
@@ +24,5 @@
> "Root actor should identify itself as a browser.");
>
> addTab(TAB_URL)
> + .then((aTab) => {
> + gTab = aTab;
Same again
::: browser/devtools/debugger/test/browser_dbg_event-listeners-03.js
@@ +24,5 @@
> "Root actor should identify itself as a browser.");
>
> addTab(TAB_URL)
> + .then((aTab) => {
> + gTab = aTab;
Again.
Attachment #8518091 -
Flags: review?(mratcliffe) → review+
Assignee | ||
Comment 28•10 years ago
|
||
Failing try run for the source-mapping tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=33232f025e27
Assignee | ||
Comment 29•10 years ago
|
||
Based on the try log, the failing seems to be caused by bug 1093535. Strangely, I cannot reproduce the issue on try. I've disabled the failing test for now and did another push to try.
Assignee | ||
Comment 30•10 years ago
|
||
Green try run for the source-mapping tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=a9478a8cf99d
Assignee | ||
Comment 32•10 years ago
|
||
Assignee | ||
Comment 33•10 years ago
|
||
Green try push for the variables-view-popup tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=8d2987c65d21
Assignee | ||
Comment 34•10 years ago
|
||
Comment 35•10 years ago
|
||
Comment 37•10 years ago
|
||
Green try run for the variables-view-filter tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=fec0804947b7
Assignee | ||
Comment 38•10 years ago
|
||
Assignee | ||
Comment 39•10 years ago
|
||
Green try run for the variables-view tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=a70cdb007874
Assignee | ||
Comment 40•10 years ago
|
||
Green try run for the tracer tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=40f7a4922b83
Assignee | ||
Comment 42•10 years ago
|
||
Assignee | ||
Comment 43•10 years ago
|
||
Comment 44•10 years ago
|
||
Assignee | ||
Comment 45•10 years ago
|
||
Green try run for the conditional-breakpoint tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=8241651b21d9
Assignee | ||
Comment 46•10 years ago
|
||
Green try run for the parser tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=0c06f46447a0
Assignee | ||
Comment 47•10 years ago
|
||
I just noticed that I was forgot to ask r+ for some of the variables-view tests, sorry about that Mike!
Attachment #8521382 -
Flags: review?(mratcliffe)
Assignee | ||
Comment 48•10 years ago
|
||
Green try run for the variables-view-* tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=47062604de60
Assignee | ||
Comment 49•10 years ago
|
||
Green try run for the watchpoint tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=adac098dcc7a
Assignee | ||
Comment 50•10 years ago
|
||
Comment 52•10 years ago
|
||
Comment on attachment 8521382 [details] [diff] [review]
Enable the variables-view-* tests
Review of attachment 8521382 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/devtools/debugger/test/head.js
@@ +970,5 @@
> waitForMessageFromTab(tab, "test:call");
> }
>
> +function evalInTab(tab, string) {
> + info("Evalling string " + string + " in tab.");
Might want to limit this dump to first n chars on first line of code to be eval'd, or else the logs might get crazy noisy for multi-line code evals.
Attachment #8521382 -
Flags: review?(mratcliffe) → review+
Assignee | ||
Comment 53•10 years ago
|
||
Assignee | ||
Comment 54•10 years ago
|
||
Green try run for the breakpoint tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=1ea4523a5267
Assignee | ||
Comment 55•10 years ago
|
||
Assignee | ||
Comment 56•10 years ago
|
||
Assignee | ||
Comment 57•10 years ago
|
||
Seeing test failures for the search tests on try (confusingly, in other tests):
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=020de4c6498c
Comment 58•10 years ago
|
||
Assignee | ||
Comment 59•10 years ago
|
||
Green try run for the search tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=f7e4f91ca819
Assignee | ||
Comment 60•10 years ago
|
||
Comment 61•10 years ago
|
||
Assignee | ||
Comment 62•10 years ago
|
||
Green try run for the stack tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=906691576d63
Assignee | ||
Comment 63•10 years ago
|
||
Some try failures for the remaining tests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=e8d23e5ad3ab
Assignee | ||
Comment 64•10 years ago
|
||
Assignee | ||
Comment 66•10 years ago
|
||
Green try run for the remaining tests after I redisabled two of them:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=6580af59fbda
Assignee | ||
Comment 67•10 years ago
|
||
Assignee | ||
Comment 68•10 years ago
|
||
With that patch, 203 out of 223 debugger tests are now running on Linux opt builds with e10s enabled. The remaining 20 tests are either blocked on bug 1093535 or have miscellaneous other issues. Finally, enabling these tests on Linux debug builds as well is blocked on bug 1073352.
Once the above patch sticks, this bug can be resolved. I'll open new bugs for enabling the remaining debugger tests for e10s and enabling the debugger tests for e10s debug builds.
Assignee | ||
Comment 69•10 years ago
|
||
Enable the debugger tests for e10s debug builds:
https://bugzilla.mozilla.org/show_bug.cgi?id=1103839
Assignee | ||
Comment 70•10 years ago
|
||
Enable the remaining debugger tests for e10s opt builds:
https://bugzilla.mozilla.org/show_bug.cgi?id=1103841
Comment 71•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 36
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•