Julian Descottes
8f89f8be90
Previously, calls to allowMatchingRejectionsGlobally would persist after a test and lead to potential failures in standalone mode. This removes the behavior and consistently clears the allowed rejections after each test. From now on, tests should explicitly call allowMatchingRejectionsGlobally and not rely on previous tests side effects. If some uncaught rejections can happen unexpectedly during a test suite, then head.js files can consistently call the API. Differential Revision: https://phabricator.services.mozilla.com/D310292