-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Moved Cluster.Sharding MNTK tests to a separate assembly #2304
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
Conversation
alexvaluyskiy
commented
Sep 10, 2016
- Moved Cluster.Sharding MNTK tests to a separate assembly
- MNTK tests should run in a specific order: Remote -> Cluster -> ClusterTools -> Sharding
@Aaronontheweb I've changed the order of MNTK tests, and the test from Cluster (LeaderElectionWithFailureDetectorPuppet) starts fail. So, It just random failing, doesn't related with Cluster.Tools or Cluster. I've found this error
I've seen this error before... in Cluster.Tools tests |
dfb6fca
to
c1b9903
Compare
c1b9903
to
648c400
Compare
mkdir testOutput | ||
let multiNodeTestPath = findToolInSubPath "Akka.MultiNodeTestRunner.exe" "bin/core/Akka.MultiNodeTestRunner*" | ||
let multiNodeTestAssemblies = !! testSearchPath | ||
let multiNodeTestAssemblies = !! "src/**/bin/Release/Akka.Remote.Tests.MultiNode.dll" ++ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should run MNTK tests in a specific order: Remote -> Cluster -> ClusterTools
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to add the sharding tests to this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But otherwise I agree with the change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sharding tests are not work at the moment. We could enable them later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They just exist
@@ -402,7 +402,7 @@ public void InitFSM() | |||
{ | |||
if (@event.StateData.RunningOp == null) | |||
{ | |||
_log.Warning("did not expect {1}", @event.FsmEvent); | |||
_log.Warning("did not expect {0}", @event.FsmEvent); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be the fix for the bug you reported