This is not part of the sbt plugin anymore. Now lives in the test conductor

since we started having multi-node tests in akka-remote-tests as well as akka-cluster, there have been port conflicts, meaning that we will not be so lucky to get away without a central communication mechanism for the TestConductor’s port number.

What are you saying? You still need to fix some port at some time? Why are they run at the same time?

The easiest solution would be to start the first TestClass in some special way and let it communicate back properties to the sbt-plugin. Still messy though.

Is this really top priority?

To allow parallel execution.

The projects akka-cluster and akka-remote-tests are tested in parallel, creating problems. The TestConductor controller should use a random port for each test suite, and that needs to be made available to the players. The only link between those is the SBT plugin, I fear.

I agree that it would be nice to run everything in parallel, but for now we could use a fixed conductor port per project (one for remote-tests and one for cluster)

Updating tickets (#2316, #641, #1936, #1939, #1941, #1942, #1945, #2010, #2049, #2052, #2058, #2120, #2121, #2126, #2140, #2142, #2143, #2149, #2151, #2176, #2274, #1792, #1940, #1943, #1112, #1938)

Updating tickets (#1939, #1941, #1942, #1945, #2017, #2052, #2058, #2126, #2140, #2142, #2176, #2274)

not needed.