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
Here's a stack trace for a timeout condition expiration.
✕ should add an empty rule row and render it properly (9169 ms)
● [E2E] rule basic UI interactions › should add an empty rule row and render it properly
TimeoutError: Waiting failed: 5000ms exceeded
at Timeout.<anonymous> (../node_modules/puppeteer/src/common/WaitTask.ts:79:11)
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 total
I'm only able to traceback the failure because that's the only statement in my test with 5000 timeout, otherwise it would be impossible to trace.
Ideally we should have either the client code lines in the stack trace, or even better allow a string parameter to be specified in the waitForFunction API to be logged upon error/timeout for debugging purposes.
The text was updated successfully, but these errors were encountered:
Feature description
Here's a stack trace for a timeout condition expiration.
Now the failing code is:
I'm only able to traceback the failure because that's the only statement in my test with 5000 timeout, otherwise it would be impossible to trace.
Ideally we should have either the client code lines in the stack trace, or even better allow a string parameter to be specified in the
waitForFunction
API to be logged upon error/timeout for debugging purposes.The text was updated successfully, but these errors were encountered: