Closed
Bug 1007006
Opened 11 years ago
Closed 11 years ago
GCLI should allow commands to be generators
Categories
(DevTools :: General, defect)
DevTools
General
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 32
People
(Reporter: jwalker, Assigned: jwalker)
References
Details
Attachments
(1 file)
5.23 KB,
patch
|
harth
:
review+
|
Details | Diff | Splinter Review |
It's as easy as slapping a Task.spawn in a host.exec thing, and it means that we can function* in our commands.
Will probably land a fix in bug 975522 because it's close to a one-liner.
Comment 1•11 years ago
|
||
Note that you can also just do
...
exec: Task.async(function* () {
...
}),
...
Assignee | ||
Comment 2•11 years ago
|
||
The change to browser_gcli_fail.js is because when Task.spawn catches the exception, it rejects the promise with ex.getMessage() which means we get an added "Error: " in the output string.
Since this should work on the web there is a new host.exec() function which just executes the function on the web, but does a Task.spawn in Firefox.
Finally there was originally a badly named host.exec() before which really spawned a new task, so that is now called host.spawn.
Attachment #8419325 -
Flags: review?(fayearthur)
Updated•11 years ago
|
Attachment #8419325 -
Flags: review?(fayearthur) → review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 3•11 years ago
|
||
Hi,
could you provide a Try link. Suggestions for what to run if you haven't
yet can be found here:
https://wiki.mozilla.org/Sheriffing/How:To:Recommended_Try_Practices
Keywords: checkin-needed
Assignee | ||
Comment 4•11 years ago
|
||
Keywords: checkin-needed
Comment 5•11 years ago
|
||
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 32
Comment 7•11 years ago
|
||
Joel, I don't think so this bug can cause those regressions in any way. DevTools are not even loaded while running such suites.
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•