-
Notifications
You must be signed in to change notification settings - Fork 59
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
aegir has a hard time letting go sometimes #212
Comments
Seen this happen on Linux and Windows now as well. |
Pretty sure I've also noticed this a few times as well on Linux, didn't pay too much attention to it as I thought it was something weird I was doing. |
Karma has some issues letting go after the test run. Ref karma-runner/karma#1788 and ampproject/amphtml#14814 This fix basically forces aegir to close after the karma tests have been successfully run, so instead of a test-run taking 13 seconds for the tests to run then 30 seconds for karma to force-close, it finishes in 14 seconds. Solves #212
The reason for that seems to be that the tests do not properly clean up (for example if the swarm is never stopped it listens for connections forever) |
Perhaps we could insert mafintosh/why-is-node-running into the test runner somehow and get it to log some output if the process doesn't exit a few seconds after the tests finish? |
Thanks @achingbrain and @mkg20001 for the tips! Seems to be quite a lot of promises (tested the e11dbf4 commit) pending, but will hopefully help to track it down |
Seems the issue is in karma somewhere, downgrading the version to |
I've been using karma 0.13.9 for some quite some time and not find any issues with existing projects. Would there be any objection if I make this downgrade and publish a new version? Reason for the downgrade is that sometimes tests that should take 3 seconds takes 2 minutes in windows. |
@victorbjelkholm What about pr #248 ? Does that solve any issues? |
@mkg20001 no, it gives bunch of output of what could be the reason behind the hang in the end, but it doesn't solve the problem itself. |
Here is one example of the output we get from
|
I frequently see on CI (Jenkins specifically) that sometimes aegir gets stuck waiting for the tests to finish when they already finished. See this example build: https://ci.ipfs.team/blue/organizations/jenkins/Multiformats%2Fjs-multihash/detail/master/5/pipeline/16
Tests actually finished after ~5 seconds, but aegir doesn't finish until ~130 seconds later, making the CI builds a lot slower than they should.
Probably a process that doesn't nicely exists, and needs to be forced kill, but there is a timeout before that force-kill happens.
I have seen this on a couple of different repositories and also on macOS workers, but seems to happen mostly on Windows.
The text was updated successfully, but these errors were encountered: