Closed Bug 1370442 Opened 8 years ago Closed 8 years ago

Permaorange browser_keybindings_01.js | Test timed out when Gecko 55 merges to beta on 2017-06-12

Categories

(DevTools :: Framework, enhancement, P1)

55 Branch
enhancement

Tracking

(firefox-esr45 unaffected, firefox-esr52 unaffected, firefox53 unaffected, firefox54 unaffected, firefox55blocking fixed)

RESOLVED FIXED
Firefox 55
Tracking Status
firefox-esr45 --- unaffected
firefox-esr52 --- unaffected
firefox53 --- unaffected
firefox54 --- unaffected
firefox55 blocking fixed

People

(Reporter: philor, Assigned: bgrins)

References

Details

Attachments

(1 file)

[Tracking Requested - why for this release]: Something that landed in the last week is going to cause permaorange https://treeherder.mozilla.org/logviewer.html#?job_id=104743767&repo=try on opt and debug, every platform, beta and devedition, when we merge to beta next week.
Sigh. [Tracking Requested - why for this release]: merge bustage, closed tree, delayed b1
needs to be addressed before 55.0b1, marking as blocker
I'm guessing this has to do with the netmonitor key change in Bug 1368734 based on where the test is failing
Priority: -- → P1
(In reply to Brian Grinstead [:bgrins] from comment #4) > Just testing a backout of > https://hg.mozilla.org/try/rev/2d566ca89b454ce2789ce93e3aa7f481bd168b06. Wrong URL, I meant: https://hg.mozilla.org/mozilla-central/rev/5be871146313 I'm not sure why that change would only affect beta builds, unless if there is some keybinding conflict with ctrl+shift+e/cmd+opt+e. Another potential cause would be a change to the debugger if it stole focus away from the toolbox
Just reproduced locally by setting the devtools.debugger.new-debugger-frontend pref to false: https://dxr.mozilla.org/mozilla-central/source/devtools/client/preferences/debugger.js#4-8
I believe this is an interaction between the keybinding change in Bug 1368734 and the fact that we only have the old debugger frontend enabled in beta. The old frontend swallows the new netmonitor shortcut As I understand it, the current plan is to enable the new debugger frontend in 56, so we only need to fix this for 55. Two main options for this that don't involve changing the old debugger ui: 1) Reorder the test in 55 so that netmonitor is tested before the debugger, acknowledging that the key shortcut won't work when the debugger is opened 2) Revert to the old shortcut in 55 Brought this up in a devtools meeting, and the team is generally leaning towards option 1 so we don't need to bump the shortcut string two more times and it won't interact with photon in m-c. I'll attach a patch for beta that does so
Assignee: nobody → bgrinstead
Blocks: 1368734
Status: NEW → ASSIGNED
Comment on attachment 8874896 [details] Bug 1370442 - Update keybindings test to always use the new debugger frontend; https://reviewboard.mozilla.org/r/146274/#review150584 ::: devtools/client/framework/test/browser_keybindings_01.js:14 (Diff revision 1) > +Services.prefs.setBoolPref("devtools.debugger.new-debugger-frontend", true); > +registerCleanupFunction(function* () { > + Services.prefs.clearUserPref("devtools.debugger.new-debugger-frontend"); > +}); Shouldn't we use something like this instead: ``` yield pushPref("devtools.debugger.new-debugger-frontend", true); ```
Attachment #8874896 - Flags: review?(pbrosset) → review+
Pushed by bgrinstead@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/364a31932fe3 Update keybindings test to always use the new debugger frontend;r=pbro
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: