-
Notifications
You must be signed in to change notification settings - Fork 111
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
Fail the build if CompletenessTest is not happy #36
Comments
Closed
I could take a look at this one. |
jbripley
pushed a commit
to jbripley/RxScala
that referenced
this issue
Oct 9, 2014
…g a default Scheduler - Changes some methods to require parentheses (timestamp, timeInterval) - Make CompletenessTest fail unit tests Fixes ReactiveX#40 and ReactiveX#36
jbripley
pushed a commit
to jbripley/RxScala
that referenced
this issue
Oct 11, 2014
…g a default Scheduler - Changes some methods to require parentheses (timestamp, timeInterval) - Make CompletenessTest fail unit tests Fixes ReactiveX#40 and ReactiveX#36
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CompletenessTest ensures that:
If any of these fails, it prints some warnings. However, now that RxScala has its own build, CompletenessTest should fail the build if it isn't happy.
The text was updated successfully, but these errors were encountered: