You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes my tests fail with: Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
at CDPSession.send (node_modules/puppeteer/lib/Connection.js:180:29)
at ExecutionContext._evaluateInternal (node_modules/puppeteer/lib/ExecutionContext.js:107:44)
at ExecutionContext.evaluate (node_modules/puppeteer/lib/ExecutionContext.js:48:23)
If I run yarn test:e2e --steps --https --port=3000 --reporter mocha-multi --serve --verbose --full-memory-crash-report on a local machine, it feels like random crashes. My project is quite fat, but I have never seen it crash like that in dev or prod env. CI pipeline is quite flaky and each test has like 5% chance to fail with a such crash.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Sometimes my tests fail with:
Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
If I run
yarn test:e2e --steps --https --port=3000 --reporter mocha-multi --serve --verbose --full-memory-crash-report
on a local machine, it feels like random crashes. My project is quite fat, but I have never seen it crash like that in dev or prod env. CI pipeline is quite flaky and each test has like 5% chance to fail with a such crash.How do I debug these crashes?
Beta Was this translation helpful? Give feedback.
All reactions