Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] TimeoutOverflowWarning: 2149630296.634 does not fit into a 32-bit signed integer. #35093

Closed
AndyGBC opened this issue Mar 7, 2025 · 3 comments · Fixed by #35096
Closed

Comments

@AndyGBC
Copy link

AndyGBC commented Mar 7, 2025

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

Windows 11
Node: v22.14.0
npm: 11.0.0
Playwright: 1.51.0
@pavelfeldman
Copy link
Member

pavelfeldman commented Mar 7, 2025

Which matches the time in milliseconds the test run has been going to the point of the output.

2149630296.634ms = 2149630s = 35000 min. Somewhere something is wrong, can you share your timeout settings?

@pavelfeldman
Copy link
Member

It could also give us more information in a raw stack if you run it with the PWDEBUGIMPL=1 env variable set.

@pavelfeldman pavelfeldman changed the title [Bug]: [BUG] TimeoutOverflowWarning: 2149630296.634 does not fit into a 32-bit signed integer. Mar 7, 2025
@pavelfeldman
Copy link
Member

The fix will be available in 1.51.1 shortly, sorry for the inconvenience!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants