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
I frequently run into test timeouts when step debugging tests.
This effectively ruins step debugging, as a TimeoutException is thrown after the first step.
We enforce timeouts via config and run tests in strict mode.
My workaround is to change the test to @large manually.
I have researched setting the timeout via cli, which could be set in PHPStorm test runner configuration for debugging.
However, --enforce-time-limit has no param and only allows the opposite. --default-time-limit <sec> - only for tests without @Small, @Medium or @large annotations.
I'd love to contribute a listener but have found no way to change the timeout configuration from inside a listener.
Any hints towards that would be appreciated.
The text was updated successfully, but these errors were encountered:
sebastianbergmann
changed the title
Disable test timeouts when using xdebug
Do not enforce time limits when a debugging session through DBGp is active
Nov 3, 2021
I have updated all maintained branches to check xdebug_is_debugger_active() and if there is an active debugging session through DBGp then execution timeouts will not be enforced.
I frequently run into test timeouts when step debugging tests.
This effectively ruins step debugging, as a TimeoutException is thrown after the first step.
We enforce timeouts via config and run tests in strict mode.
My workaround is to change the test to
@large
manually.I have researched setting the timeout via cli, which could be set in PHPStorm test runner configuration for debugging.
However,
--enforce-time-limit
has no param and only allows the opposite.--default-time-limit <sec>
- only for tests without @Small, @Medium or @large annotations.I'd love to contribute a listener but have found no way to change the timeout configuration from inside a listener.
Any hints towards that would be appreciated.
The text was updated successfully, but these errors were encountered: