-
Notifications
You must be signed in to change notification settings - Fork 47
Error: EAGAIN: resource temporarily unavailable, write #38
Comments
the same problem with node v4.3 |
ping :) |
Same issue on 5.11.1 |
What version of karma-teamcity-reporter are you using? Seems some errors were fixed in the latest versions. |
I'm getting this same error, using these versions:
I'm using node 6.4.0 and CentOS 5.11. |
I found this repo which reproduces the error: https://github.com/vlki/karma-teamcity-reporter-node6-error - however, I had to increase the number of tests in test.js significantly before the error happened on my machine, although with 8000 or so tests it is failing consistently for me. If I use karma-teamcity-reporter 0.1.2 then the error goes away (this is before writeSync started being used in d8d9e70). |
Same error is reproducing for: "karma-teamcity-reporter": "1.0.0" node:5.10.1 We have over 2500 tests, and the error happens randomly. Downgrading to karma-teamcity-reporter 0.1.2 have fixed the issue. (Which is relying in the standard write mechanism from Karma. process.stdout.write) |
Also create html page to run tests interactively in browser. Use karma-teamcity-reporter 0.1.2 to workaround karma-runner/karma-teamcity-reporter#38
Also create html page to run tests interactively in browser. Use karma-teamcity-reporter 0.1.2 to workaround karma-runner/karma-teamcity-reporter#38
Also create html page to run tests interactively in browser. Use karma-teamcity-reporter 0.1.2 to workaround karma-runner/karma-teamcity-reporter#38
Also create html page to run tests interactively in browser. Use karma-teamcity-reporter 0.1.2 to workaround karma-runner/karma-teamcity-reporter#38
Also create html page to run tests interactively in browser. Use karma-teamcity-reporter 0.1.2 to workaround karma-runner/karma-teamcity-reporter#38 (cherry picked from commit 325ebfb)
Also create html page to run tests interactively in browser. Use karma-teamcity-reporter 0.1.2 to workaround karma-runner/karma-teamcity-reporter#38 (cherry picked from commit 325ebfb)
Is it possible to introduce some retry logic in case if EAGAIN is encountered? |
+1 |
This error started to appear when updated to node 6.0
It appears randomly when executing a large set of tests.
This is the full stack of the error:
The text was updated successfully, but these errors were encountered: