As can be seen from the first round of testing in PR #15864, trying to update Puppeteer beyond version `19.0.0` completely breaks testing in Firefox. Curiously it does work locally when the `--noChrome` flag is being used, so it seems to be an issue with running tests in both Chrome *and* Firefox in parallel.

We need to fix this, likely by making some adjustments to our test-suite, such that we don't get "stuck" on an older version of Puppeteer without being able to update. (A temporary work-around could also be to disable testing in Chrome.)

}
    if (pathname === "/info") {
      console.log(data.message);
      return;
    }
    var session = getSession(data.browser);
    session.numRuns++;
    var message =
      data.status + " | " + data.description + " | in " + session.name;
    if (data.status === "TEST-UNEXPECTED-FAIL") {
      session.numErrors++;
    }
    if (data.error) {
      message += " | " + data.error;
    }
    console.log(message);
  });
  return true;
}
async function startBrowser(browserName, startUrl = "") {
  const revisions =
    require("puppeteer-core/lib/cjs/puppeteer/revisions.js").PUPPETEER_REVISIONS;
  const wantedRevision =
    browserName === "chrome" ? revisions.chromium : revisions.firefox;
  
  
  
  const browserFetcher = puppeteer.createBrowserFetcher({
    product: browserName,
  });