Closed Bug 1072141 Opened 6 years ago Closed 6 years ago
browser/webaudioeditor tests fail in e10s
Most of the necessary changes are shallow and very similar to bug 1065355 (and hence requesting review from Patrick again!) Note however there is also a change to toolkit/devtools/server/actors/webaudio.js, which moves the null-ing of this.tabActor to after this.tabActor is passed to off(). With these changes the tests all pass locally for me with e10s enabled.
Attachment #8494327 - Flags: review?(pbrosset)
Comment on attachment 8494327 [details] [diff] [review] 0001-Bug-XXXXXXX-get-browser-devtools-webaudioeditor-test.patch Review of attachment 8494327 [details] [diff] [review]: ----------------------------------------------------------------- Yep, that does look exactly like bug 1065355 and since no test actually use debuggee, it's the perfect fix for this. Thanks!
Attachment #8494327 - Flags: review?(pbrosset) → review+
You're welcome :) https://hg.mozilla.org/integration/fx-team/rev/6d9fb906e5b9
Assignee: nobody → mhammond
Status: NEW → ASSIGNED
Points: --- → 2
sorry had to backout this change for test failures like https://tbpl.mozilla.org/php/getParsedLog.php?id=48757407&tree=Fx-Team
The tests in browser/devtools/webaudioeditor/test/browser_audionode-actor-get-param-flags.js were not running at all. This was because: - An attempt was made to yield inside an Array.forEach (not valid... prevents the JS engine from entering the loop). - nodes[i].getParamFlag(param) should have been nodes[i].getParamFlags(param) (the error was not visible because the browser never entered the loop). Spoke with markh who seems happy for me to add it to this bug.
Looks like the same fixes (as debuggee is never used) as bug 1061904, so closing that one (was waiting for refactoring bug 1057042 to land, but that just landed)
Comment on attachment 8494507 [details] [diff] [review] fix_browser_audionode-actor-get-param-flags-js.patch Sorry to mess you around Mike, but if it's OK, can you please put this new patch into a different bug, as I'm going to reland the larger patch.
Relanded with the tests I mysteriously missed fixed in the same way, so carrying r= forward. Try at https://tbpl.mozilla.org/?tree=Try&rev=1f6e18d9d4c8
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35
You need to log in before you can comment on or make changes to this bug.