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
After investigating a strange behavior on running karma with TeamCity on Windows, I noticed the following issue.
When running the following command in PowerShell:
karma start --single-run | Out-File C:\test.out
The writing function is non-blocking/asynchronous & the written/piped data can be buffered, which could lead to some test results being lost.
Karma needs to ensure that all buffers have been drained or that the writing functions have completed (if they are non-blocking) before exiting the process.
The text was updated successfully, but these errors were encountered:
) which is used by all the components in the system to delay exit (eg. reporters writing a file). In the same way, we should wait for process.stdout to drain.
After investigating a strange behavior on running karma with TeamCity on Windows, I noticed the following issue.
When running the following command in PowerShell:
The writing function is non-blocking/asynchronous & the written/piped data can be buffered, which could lead to some test results being lost.
Karma needs to ensure that all buffers have been drained or that the writing functions have completed (if they are non-blocking) before exiting the process.
The text was updated successfully, but these errors were encountered: