The `TEST-UNEXPECTED-FAIL | checks that docIds are unique and increasing | in chrome | Expected 9 to be less than 0` unit test failed in a recent test run in https://github.com/mozilla/pdf.js/pull/13837#issuecomment-890511627, but also locally once for me. Perhaps this goes wrong because the test depends on state that might be mutated if the tests are shuffled?

/cc @Snuffleupagus since this unit test was added in https://github.com/mozilla/pdf.js/pull/13813/commits/b18620ac0f196c6fa5a9e54a53fa6b915e19e843
expect(reason instanceof PasswordException).toEqual(true);
            expect(reason.code).toEqual(PasswordResponses.NEED_PASSWORD);
            return passwordNeededDestroyed;
          }
        );
        passwordIncorrectLoadingTask.onPassword = function (callback, reason) {
          if (reason === PasswordResponses.INCORRECT_PASSWORD) {
            throw new Error("Incorrect password");
          }
          
          expect(false).toEqual(true);
        };
        const result2 = passwordIncorrectLoadingTask.promise.then(
          function () {
            
            expect(false).toEqual(true);
            return Promise.reject(new Error("loadingTask should be rejected"));
          },
          function (reason) {
            expect(reason instanceof PasswordException).toEqual(true);
            expect(reason.code).toEqual(PasswordResponses.INCORRECT_PASSWORD);
            return passwordIncorrectLoadingTask.destroy();
          }
        );
        await Promise.all([result1, result2]);
      }
    );
    it("creates pdf doc from empty typed array", async function () {
      const loadingTask = getDocument(new Uint8Array(0));
      try {