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
progressReportedCapability.resolve(data);
      };
      const data = await Promise.all([
        loadingTask.promise,
        progressReportedCapability.promise,
      ]);
      expect(data[0] instanceof PDFDocumentProxy).toEqual(true);
      expect(data[1].loaded / data[1].total).toEqual(1);
      await loadingTask.destroy();
    });
    it("creates pdf doc from invalid PDF file", async function () {
      
      const loadingTask = getDocument(buildGetDocumentParams("bug1020226.pdf"));
      try {
        await loadingTask.promise;
        
        expect(false).toEqual(true);
      } catch (reason) {
        expect(reason instanceof InvalidPDFException).toEqual(true);
        expect(reason.message).toEqual("Invalid PDF structure.");
      }
      await loadingTask.destroy();
    });
    it("creates pdf doc from non-existent URL", async function () {
      if (!isNodeJS) {
        
        pending("Fails intermittently on Linux in browsers.");
      }
      const loadingTask = getDocument(
        buildGetDocumentParams("non-existent.pdf")