Closed Bug 773161 Opened 14 years ago Closed 14 years ago

Intermittent browser_gcli_addon.js | Test timed out

Categories

(DevTools :: Console, defect, P3)

x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 18

People

(Reporter: philor, Assigned: miker)

References

Details

(Keywords: intermittent-failure, Whiteboard: [fixed-in-fx-team])

Attachments

(1 file, 2 obsolete files)

https://tbpl.mozilla.org/php/getParsedLog.php?id=13448305&tree=Mozilla-Inbound Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound opt test mochitest-other on 2012-07-11 21:55:06 PDT for push 264e13c78fee slave: talos-r4-snow-079 TEST-START | chrome://mochitests/content/browser/browser/devtools/commandline/test/browser_gcli_addon.js error In screenshot/fullpage: boolean parameters can not have a defaultValue. Ignoring error In restart/nocache: boolean parameters can not have a defaultValue. Ignoring TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/commandline/test/browser_gcli_addon.js | Test timed out (screenshot) warn: Failed to remove handler from Inputter.onResize warn: Failed to remove handler from CommandAssignment.onAssignmentChange INFO TEST-END | chrome://mochitests/content/browser/browser/devtools/commandline/test/browser_gcli_addon.js | finished in 30066ms
Mike: What would happen if the addon system called AddonManager.getAllAddons very late? Like after the tests had started running? Perhaps this is a result of lack of async types?
Depends on: 685526
Priority: -- → P3
Target Milestone: --- → Future
At the end of our call to getAllAddons we send a notification (gcli_addon_commands_ready) and the tests do not begin until this notification is received. I suspect that this issue is caused by the command completing it's loading before the test is run (getAllAddons is running too early). We need the gcli_addon_commands_ready notification so that we know when getAllAddons finishes running, I guess we need some way to know if getAllAddons has already run.
Assignee: nobody → mratcliffe
Status: NEW → ASSIGNED
I have added a gcli.addonsLoaded flag so that we can fire a gcli_addon_commands_ready notification in the event that one was sent before the test started running.
Attachment #655945 - Flags: review?(jwalker)
Comment on attachment 655945 [details] [diff] [review] Added gcli.addonsLoaded to determine whether getAllAddons is already complete Review of attachment 655945 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/devtools/commandline/test/browser_cmd_addon.js @@ +96,5 @@ > }); > > Services.obs.addObserver(GAT_ready, "gcli_addon_commands_ready", false); > + > + if (imported.gcli.addonsLoaded) { I like it except that we're using GCLI as a place to store a flag that is of use only to the addon command. Would it work to use an object exported from CmdAddon to store this flag?
Attachment #655945 - Flags: review?(jwalker)
Attachment #655945 - Attachment is obsolete: true
Attachment #658048 - Flags: review?(jwalker)
Attachment #658048 - Attachment is obsolete: true
Attachment #658048 - Flags: review?(jwalker)
Attachment #658049 - Flags: review?(jwalker)
Attachment #658049 - Flags: review?(jwalker) → review+
Whiteboard: [orange] → [orange][land-in-fx-team]
Whiteboard: [orange][land-in-fx-team] → [orange][fixed-in-fx-team]
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: Future → Firefox 18
Whiteboard: [orange][fixed-in-fx-team] → [fixed-in-fx-team]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: