-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Implemented DeterministicOldestWhenJoiningSpec #2101
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
You can reset the git timestamp using this technique: http://stackoverflow.com/a/31540373/377476 - that way CI can pick up the commit and run. |
ee816e7
to
9b3e442
Compare
Take a look at the failed cluster domain event specs in the unit tests - looks like there are some issues there. |
f976786
to
6e74ae1
Compare
@alexvaluyskiy have you tried rebasing this with your latest changes yet? |
Yep, no changes |
de0495b
to
736e444
Compare
736e444
to
6b755cd
Compare
@Aaronontheweb ready for review |
@alexvaluyskiy got it! |
Joining_cluster_must_result_in_deterministic_oldest_node(); | ||
} | ||
|
||
public void Joining_cluster_must_result_in_deterministic_oldest_node() |
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.
Spec looks good
Solid work. The changes make sense to me - I'll pull this into my work on the transition spec as well. |
Fixed #2082
Should go after these two: #2098 and #2099