33 and newer are affected, 31, 31ESR and 32 are not affected. Regression: m-c: Last good revision: 9305a8ec77fe (2014-06-09) First bad revision: 9dc0ffca10f4 (2014-06-10) Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9305a8ec77fe&tochange=9dc0ffca10f4 m-i: Last good revision: 2d7dcf4f98b8 First bad revision: 7cf9d4063533 Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=2d7dcf4f98b8&tochange=7cf9d4063533 fx-team: Last good revision: d31f7a547ab0 First bad revision: 6e5607b09d8f Pushlog: https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=d31f7a547ab0&tochange=6e5607b09d8f 6e5607b09d8f Joe Walker — Bug 992309 - Don't leak gcli promise to other tests; r=mratcliffe Maybe other commands are affected too.
[Tracking Requested - why for this release]:
status-firefox33: --- → affected
tracking-firefox34: --- → ?
tracking-firefox35: --- → ?
tracking-firefox36: --- → ?
Version: unspecified → 33 Branch
Joe - is this something we could backout of 34? We're almost done with Beta so only a low risk backout would be possbile there.
status-firefox34: --- → affected
status-firefox35: --- → affected
status-firefox36: --- → affected
tracking-firefox35: ? → +
tracking-firefox36: ? → +
I don't think we should back this out. It's a fairly invasive patch and has lots of side-effects. We do need to fix it properly.
I think we can take a trivial or very small fix if one can be made available today. However, I also think that we can ship with this bug (we already have) and that that is the most likely option. If we get many user complaints on 34 we should direct people to try the developer edition until 35 is out.
tracking-firefox34: ? → ---
Given this is a developer tools issue, not a wide-facing user issue, there's no need to track this regression for a specific release. Dev tools teams can prioritize this and nominate for uplift consideration when fixed if low risk.
tracking-firefox35: + → -
tracking-firefox36: + → -
In Nightly 41, I now see the available options again. Please re-open if this is still an issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
Buggy, but it is back, yes.
You need to log in before you can comment on or make changes to this bug.