[Bug]: v19.8.1

[WilcoFiers]

Bug expectation

Puppeteer to run when upgrading from 19.8.0 to 19.8.1.

It looks like a cache problem. When I install 19.8.1 without cache I get this error. If I look at the cache the revision it says it needs is there. It doesn't seem to pick up on it. When I install 19.8.0 first, and then install 19.8.1 on top things do work.

Bug behavior

• Flaky
• PDF

Minimal, reproducible example

const puppeteer = require('puppeteer');

(async () => {
  let browser;
  try {
    browser = await puppeteer.launch();
    const page = await browser.newPage();
    await page.goto('https://www.google.com/');
  } finally {
    if (browser) await browser.close();
  }
})().catch(err => {
  console.error(err.stack);
  process.exit(1);
});

Error string

Could not find Chromium (rev. 1108766). This can occur if either 1. you did not perform an installation before running the script (e.g. npm install) or 2. your cache path is incorrectly configured (which is: /home/wilco/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.

Puppeteer configuration

None, just the default.

Puppeteer version

19.8.1

Node version

v16.15.0

Package manager

npm

Package manager version

8.19.1

Operating system

macOS

[github-actions]

This issue was not reproducible. Please check that your example runs locally and the following:

• Ensure the script does not rely on dependencies outside of puppeteer and puppeteer-core.
• Ensure the error string is just the error message.

  • Bad:

    Error: something went wrong
      at Object.<anonymous> (/Users/username/repository/script.js:2:1)
      at Module._compile (node:internal/modules/cjs/loader:1159:14)
      at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
      at Module.load (node:internal/modules/cjs/loader:1037:32)
      at Module._load (node:internal/modules/cjs/loader:878:12)
      at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
      at node:internal/main/run_main_module:23:47

  • Good: Error: something went wrong.

• Ensure your configuration file (if applicable) is valid.
• If the issue is flaky (does not reproduce all the time), make sure 'Flaky' is checked.
• If the issue is not expected to error, make sure to write 'no error'.

Once the above checks are satisfied, please edit your issue with the changes and we will
try to reproduce the bug again.

---

Analyzer run

[OrKoN]

Thanks for the report. This is being addressed with #9939. Originally reported in #9917 (comment)