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
);
      const renderTask = pdfPage.render({
        canvasContext: canvasAndCtx.context,
        canvasFactory: CanvasFactory,
        viewport,
      });
      
      renderTask.onContinue = function (cont) {
        waitSome(cont);
      };
      try {
        await pdfDoc.cleanup();
        
        expect(false).toEqual(true);
      } catch (reason) {
        expect(reason instanceof Error).toEqual(true);
        expect(reason.message).toEqual(
          "startCleanup: Page 1 is currently rendering."
        );
      }
      await renderTask.promise;
      CanvasFactory.destroy(canvasAndCtx);
      await loadingTask.destroy();
    });
    it("caches image resources at the document/page level as expected (issue 11878)", async function () {
      const { NUM_PAGES_THRESHOLD } = GlobalImageCache,
        EXPECTED_WIDTH = 2550,
        EXPECTED_HEIGHT = 3300;
      const loadingTask = getDocument(buildGetDocumentParams("issue11878.pdf"));
      const pdfDoc = await loadingTask.promise;