Puppeteer-related CI failures

[thompsongl]

Noticing an increase in CI failures (both jobs) due to Puppeteer-Chromium download errors:

Example:

09:30:03 error /app/node_modules/puppeteer: Command failed.
09:30:03 Exit code: 1
09:30:03 Command: node install.js
09:30:03 Arguments: 
09:30:03 Directory: /app/node_modules/puppeteer
09:30:03 Output:
09:30:03 ERROR: Failed to download Chromium r706915! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.
09:30:03 Error: end of central directory record signature not found
09:30:03     at /app/node_modules/yauzl/index.js:167:14
09:30:03     at /app/node_modules/yauzl/index.js:473:5
09:30:03     at /app/node_modules/fd-slicer/index.js:32:7
09:30:03     at FSReqWrap.wrapper [as oncomplete] (fs.js:467:17)
09:30:03   -- ASYNC --
09:30:03     at BrowserFetcher.<anonymous> (/app/node_modules/puppeteer/lib/helper.js:111:15)
09:30:03     at Object.<anonymous> (/app/node_modules/puppeteer/install.js:62:16)
09:30:03     at Module._compile (internal/modules/cjs/loader.js:778:30)
09:30:03     at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
09:30:03     at Module.load (internal/modules/cjs/loader.js:653:32)
09:30:03     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
09:30:03     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
09:30:03     at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
09:30:03     at startup (internal/bootstrap/node.js:283:19)
09:30:03     at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)

No initial thoughts on a cause or remedy.

[thompsongl]

Error: end of central directory record signature not found

^ is the telling part. It means that the downloaded Chromium zip file is corrupted or incomplete. Research indicates that intermittent network issues are to blame, matching the inconsistency with which we see the failure.

The one true workaround (Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download) is a non-option because our automated axe testing suite uses Chromium.

Still looking for a solution

[github-actions]

👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.

[thompsongl]

Keep this open for now. There are soon-to-be-merged PRs that might improve CI performance and make this issue less prevalent.

[github-actions]

👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.

[thompsongl]

See my earlier comment on the likely cause, but it's unlikely we find a fix. It's become much less common for this failure to occur so I'm closing and we can readdress if that trend discontinues.