Skip to content
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

Node generation and testing updates #16

Merged
merged 6 commits into from
Feb 2, 2012
Merged

Conversation

seancribbs
Copy link
Contributor

This branch contains a number of important patches (but most importantly, introduces a green build!

  • Node generation default settings are in sync with 1.0.3 and the to-be-released 1.1.0.
  • The Riak version can be detected before a node is generated.
  • Node/test-server generation works for 0.14.x. This includes a 0.14.x-specific test backend.
  • Examples can be tagged with a minimum version number or a range of versions so that we skip integration tests that will fail against the configured test server.
  • Intermittently failing examples can be automatically retried with the sometimes example declaration, and the number of retries can be specified as the :retries metadata. Retried examples will be reported at the end of the suite.

Reviewers: After code/style review, please run the suite against Riak 0.14.2, 1.0.3 and master (1.1) to verify.

example_to_run.run
break unless self.example.exception
end
if e = self.example.exception
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doing an assignment operation in an if clause?

@seancribbs
Copy link
Contributor Author

Any other comments? /cc @myronmarston @ntalbott @aphyr

seancribbs added a commit that referenced this pull request Feb 2, 2012
Node generation and testing updates
@seancribbs seancribbs merged commit 4445463 into master Feb 2, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant