1.51.0
Steps to reproduceHave a test suite that run for longer than 34+ minutes (roughly).
Expected behaviorI do not expect to see that error.
Actual behaviorI 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 contextNo response
EnvironmentWindows 11 Node: v22.14.0 npm: 11.0.0 Playwright: 1.51.0
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4