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
We talked about addressing this by watching a couple of Node events and, if some threshold of time elapses between them, letting the user know what's happening. Optionally we could fulfill the promise so Node forcibly returns.
The text was updated successfully, but these errors were encountered:
@ericsciple We are also facing the same issue in test execution task. If test code leaves any stale process (typically chrome driver), we end up hitting task timeout in the end even though test execution is completed.
On Linux, the test agents hang indefinitely under the following conditions:
See https://github.com/natemcmaster/repro-vsts-stdout-blocking
We talked about addressing this by watching a couple of Node events and, if some threshold of time elapses between them, letting the user know what's happening. Optionally we could fulfill the promise so Node forcibly returns.
The text was updated successfully, but these errors were encountered: