simple test config setup. see test_config_basic.py for use
forgot this
show that you can extract something out of a param dictionary in the json
do verify_cloud_size() as well as checking the sandbox (every 60 secs) to make sure h2o is still there
add param for timeoutSecs to verify_cloud_size()/get_cloud()
add a little rf to the example
add deleting keys in the teardown, and add the other subtests from test.py, into the example
print out the url to browse the cloud like michal (the port changes)
I didn't push these
tom wanted configuration dependent key delete at end of release tests. do it with cloud build state: delete_keys_at_teardown, which is passed thru the json like any othe python node state, to the test with the cloned cloud.
then that's used in h2o_common.py to decide what to do in tearDownClass. assumes you're using h2o_common.py like in test_release_basic.py (although you could just copy/paste and use without the common)
tom will say it's bloated, but a little test
enable the side logging for performance tracking in the no-cloud-build test
try an automatic cloud restart after failure
do some checking of what I think is the current requirement for command line args (at java -jar time) if you do a maprfs/s3n/s3/hdfs import at runtime. just print error for now
fixes from test.0xdata.com mostly around testdir_hosts and new s3/s3n tests
updated test lists
add new test_rf_predict2.py to do an exact compare of the original iris2.csv output col and the predicted value after downloading to csv, and check they match for all rows (100% predict, given trained on full dataset)
Merge remote-tracking branch: upstream/master