On Mon, Apr 4, 2016 at 10:07 AM, Nick Fitzgerald
<
nfitz...@mozilla.com> wrote:
> Why was it accidentally disabled, and how can we prevent that accidentally
> happening again?
It was accidentally disabled by changing the DevTools loader to
instantiate its own instance of Promise.jsm, instead of using the one
from the outer context that the rest of the browser is using. We need
to use the outer instance of Promise.jsm because that's the one the
test harness uses to wire up the tracking of unhandled rejections that
trigger test failures.
As you can see from the patch to re-enable it[1], the change seems
quite benign, and it's not obvious that this would have any effect on
the test harness at all.
As for preventing future regressions, I am not sure exactly... I guess
having a new test that rejects a promise and ensures there is a
failure is the best approach. I'd have to investigate that a bit to
see the best way to ensure a certain number of failures are reported
by the test harness.
[1]:
https://hg.mozilla.org/mozilla-central/rev/4317688957ef
- Ryan