Backstop - occasional "Failed to launch the browser process" errors

[mcoker]

trafficstars

The error

x Close Browser
x Close Browser
SCENARIO > 733 of 998 - /layouts/level/html/two-items (mobile)
SCENARIO > 733 of 998 - /layouts/level/html/two-items (tablet)
x Close Browser
x Close Browser
x Close Browser
      COMMAND | Command "test" ended with an error after [808.498s]
      COMMAND | Error: Failed to launch the browser process!
                
                
                TROUBLESHOOTING: https://pptr.dev/troubleshooting
                
                    at Interface.onClose (/Users/cmichael/repos/patternfly/node_modules/@puppeteer/browsers/lib/cjs/launch.js:310:24)
                    at Interface.emit (node:events:531:35)
                    at Interface.close (node:internal/readline/interface:528:10)
                    at Socket.onend (node:internal/readline/interface:254:10)
                    at Socket.emit (node:events:531:35)
                    at endReadableNT (node:internal/streams/readable:1696:12)
                    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
SCENARIO > 733 of 998 - /layouts/level/html/two-items (desktop)
SCENARIO > 734 of 998 - /layouts/level/html/three-items (tablet)
SCENARIO > 734 of 998 - /layouts/level/html/three-items (mobile)
x Close Browser
x Close Browser
SCENARIO > 735 of 998 - /layouts/level/html/with-gutters (mobile)

Things I've tried

• Updated backstop to latest
• Upgrade chromium
• Install as regular package as well as from homebrew
• Define explicit path to chromium
• Use headless: true instead of "new"
• Added ignoreDefaultArgs: ['--disable-extensions']
• Deleted node_modules/puppeteer, in an attempt to make sure the puppteeer version is from from node_modules/backstopjs/node_modules/puppeteer
• Deleted node_modules/backstopjs/node_modules/puppeteer and installed latest puppeteer in root of PF project
• Up

Things I haven't tried

• Go back to previous versions of PF to see if it runs in any of them
• Downgrade backstop version
• I read something about some kind of cache/data directory that can sometimes trigger this kind of error?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 60 days.

[mcoker]

Closing, haven't seen this in a while.