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
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
We've been seeing an issue with the reporter failing to show a report at the end of a test run.
At the moment, this only happens when using a remote selenium server with the test code running on the local machine.
The cause of the issue seems to be the timeout setting in function:
The child process fires all of its test run messages to the parent in quick succession, but because of the 5sec timeout, never has a chance to get a response from the parent which means no test results in the console. Raising the timeout to 30sec didn't help. Screenshot of a test run with no output.
Removing the timeout completely does solve the issue, but doesn't address the underlying problem that the parent process takes a very long time to respond to the messages.
Node docs indicate this happens when the IPC backlog exceeds a threshold, or parent has exited. Since messages are processed given enough time, points to the IPC backlog being full.
For the moment we're simply going to remove the timeout from local code, but a long term solution is needed.
P.S
For reference, I found this after writing the issue. I understand the timeout was explicit, but in that case it means the parent shouldn't exit until all received messages have been handled and displayed. e4000cf
The text was updated successfully, but these errors were encountered:
We've been seeing an issue with the reporter failing to show a report at the end of a test run.
At the moment, this only happens when using a remote selenium server with the test code running on the local machine.
The cause of the issue seems to be the timeout setting in function:
The child process fires all of its test run messages to the parent in quick succession, but because of the 5sec timeout, never has a chance to get a response from the parent which means no test results in the console. Raising the timeout to 30sec didn't help. Screenshot of a test run with no output.
Removing the timeout completely does solve the issue, but doesn't address the underlying problem that the parent process takes a very long time to respond to the messages.
Debugging this a little further, we noticed that this line returns
false
when firing messages to the parent.https://github.com/webdriverio/wdio-mocha-framework/blob/master/lib/adapter.js#L239
Node docs indicate this happens when the IPC backlog exceeds a threshold, or parent has exited. Since messages are processed given enough time, points to the IPC backlog being full.
For the moment we're simply going to remove the timeout from local code, but a long term solution is needed.
P.S
For reference, I found this after writing the issue. I understand the timeout was explicit, but in that case it means the parent shouldn't exit until all received messages have been handled and displayed.
e4000cf
The text was updated successfully, but these errors were encountered: