test_slice_fail_1161.py is for hex-1161 (simplification of test_rf_covtype_train_oobe2.py and ..oobe3.py fails.
I reduced the tree depth on test_rf_big_rand_tree.py to avoid GC/out of memory for the 7 gb heaps used.
Merge branch 'master' of github.com:0xdata/h2o
two variants for hex-1161 (exec slice issue)
More GBM classification-vs-regression work

Start pushing regression thru SharedTreeModelBuilder
Merge branch 'master' of github.com:0xdata/h2o
add info for hdfs_version and hdfs_name node to the find_cloud so the different runners and python tests will import hdfs correctly...also added expected_size to find_cloud.py to check the cloud is sane before doing tests
Push regression GBM thru to 1st results
Merge branch 'master' of github.com:0xdata/h2o
kill_all* ..do what it says. the others, remove unnecessary line
do the maprfs test first so we can see if it works better on jenkins now
don't do RF (one of the datasets has reals..just turn off RF for now)
Run a regression GBM
Merge branch 'master' of github.com:0xdata/h2o
GLM2 update. Got incremental validation during model building.
Bugfix in Parse2. Added missing DKV.puts on the enum vecs after renumbering.
h2o.gbm argument checking r unit
Merge branch 'master' of https://github.com/0xdata/h2o
seems like we want to check the sandbox on the connection resets. we may exception out of python too quickly before h2o can dump a gc/out of memory error to it's stdout. Special case the exception on the do_json_request, (try/catch) and wait a second and check the sandbox for errors. print a red message before we do that. That branch isn't taking if ignoreConnectionError, which is used when polling h2o during bringup, when connection exceptions are expected (they used to be ignored at a higher level ..i.e. at stabilize_cloud() etc.
Merge branch 'master' of github.com:0xdata/h2o
Using H2O_HOSTS_FILE to point to host file location.