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
akka-actor-tests fails - "Coroner not cancelled after 60000ms" #21375
Comments
That is "just" a warning that the test is taking longer than expected. Does it always take that long, and do you see same in the Jenkins logs https://jenkins.akka.io:8498/job/akka-multi-node-nightly/ ? |
I do always see that output I gave above. I don't know how long it takes because I've never seen it finish. Does the suite really take nearly two hours to run, or am I reading that Jenkins graph wrong? |
This time I got a completion, with failures:
Some excerpts from higher up in the test output:
|
After doing a full compile of the other modules, I'm down to only one failure.
This test runner doesn't print out the details for the failing tests at the end? Running it again with output piped to a file, because I think the error is too far up to scroll back to... |
Ah, here we go.
Do certain ports need to be unbound for the tests to pass? |
I guess that was port 23402 still bound by a previous instance of SBT that didn't kill all the way. Once I kill that, I'm back to the original behavior; it gets to that test and then hangs (seemingly) indefinitely.
|
We try to avoid fixed ports, but I see that this test is not following that recommendation. It should be possible to replace that hardcoded 23402 with |
I left this test to run overnight, and it has not yet halted. |
Was there more issues than the hardcoded port in this ticket or should I close it? |
Yeah, the issue as I first reported it still stands. When I run the tests, they always stop at that point and never complete. The port issue I only encountered due to a previous SBT instance that was still running as a result of the test suite never halting. |
I think this is mainly about having a machine that is vastly different (cpu speed/cores, amount of memory etc. os) from the ones we develop on and the ci-servers (which are really slow though) making the timing assumptions in the tests unstable for your env. Did you try running it with a higher test time factor?( |
Two possible races in TcpSpec fixed in #21685 that may relate to this ticket. |
* problem occurs when network is offline * use socket timeout * additional cleanup of socket utils
problem occurs when network is offline, I have fixed it in #21816 |
* use socket timeout * additional cleanup of socket utils
* use socket timeout * additional cleanup of socket utils
When I run
akka-actor-tests/test
in SBT on the master branch, after a while I get the following output and then execution hangs indefinitely.Am I doing something wrong? Are the tests just not working right now? Is there a CI server with the build status somewhere?
The text was updated successfully, but these errors were encountered: