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
Karma sometimes generates Error: read ECONNRESET after successful test run #3295
Comments
I'm surprised by this part of the output:
Is the 'progress' reporter running? It looks like the test executes and passes, so perhaps the browser is being killed out of order withh the socket close? Try running with logLevel debug and compare error and not-error cases. |
Sorry, the |
Here are the logs for both the failure case and success case. |
The key parts: SUCCESS: So it looks like the launcher kills the chrome process but the server does not know that the socket is dying on purpose. So the launcher and the server race to the next event. If the launcher wins, success. If the server wins fail. |
Can or will this issue be addressed at some point? Is there a work around? |
This issue seems to be only about an annoying and erratic error message. |
Karma sometimes reports uncaught exceptions (ECONNRESET) which causes it to exit the process with a non-zero exit code. Fixes karma-runner#3295
@johnjbarton I sent a PR to fix this issue. This is currently making our automated tests fail because we rely on the exit code being 0. |
Since upgrading to Angular 11 we are experiencing this problem. I've verified a few things:
Will this PR be merged soon? We'd really appreciate it! |
Sorry which PR has a proposed fix? |
@johnjbarton This is the PR: #3402 |
Any update on this? This is still messing up the build on some comps. |
End of 2022 and this is still an issue. Started in our project like a week ago. Causes our local builds to fail but runs on Jenkins without any problems. Edit: for more context: it stopped working locally, randomly, last week. Maybe it has something to do with a Chrome update? Our Jenkins runs on an older Chrome where it still works flawlessly but locally multiple devs suddenly got problems. (Current, not working Chrome build: 106.0.5249.121. My colleague has 107.0.5304.88 and it's not working for them, either.) |
Expected behaviour
This started happening intermittently after I upgrade from 3.1.3 to 3.1.4, and it has been happening ever since (not every time -- about 1/3 to 1/2 of the time). ( After looking through the changelog, I'm inclined to suspect cc2eff2 )
The error I get is:
Actual behaviour
Error: read ECONNRESET
Environment Details
Karma version: 4.0.1
Operating System: Windows 10 64-bit
See: https://stackoverflow.com/questions/54809981/how-do-i-debug-errors-from-karma-server
Steps to reproduce the behaviour
Unfortunately I cannot share my repo, since it is private. If someone can guide me on how to track down the source of this error, I'd be happy to do the heavy lifting.
The text was updated successfully, but these errors were encountered: