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
Have a test suite that run for longer than 34+ minutes (roughly).
Expected behavior
I do not expect to see that error.
Actual behavior
I have a regression test suite of 500+ tests. These have been running/passing just find on 1.49.0 but today I updated to 1.51.0.
After around 118 tests , the VS Code terminal shows this output: (node:16668) TimeoutOverflowWarning: 2149630296.634 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Which matches the time in milliseconds the test run has been going to the point of the output. The test that is running when it happens fails, but then the test run continues on.
Additional context
No response
Environment
Windows 11
Node: v22.14.0
npm: 11.0.0
Playwright: 1.51.0
The text was updated successfully, but these errors were encountered:
Version
1.51.0
Steps to reproduce
Have a test suite that run for longer than 34+ minutes (roughly).
Expected behavior
I do not expect to see that error.
Actual behavior
I have a regression test suite of 500+ tests. These have been running/passing just find on 1.49.0 but today I updated to 1.51.0.
After around 118 tests , the VS Code terminal shows this output:
(node:16668) TimeoutOverflowWarning: 2149630296.634 does not fit into a 32-bit signed integer. Timeout duration was set to 1.
Which matches the time in milliseconds the test run has been going to the point of the output. The test that is running when it happens fails, but then the test run continues on.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: