I Hate Git, all my files are not pushed
michal made me do it. add the build_cloud_with_hosts option to the rest of the testdir_single_jvm tests
so they can all be run with -cj <config json> option to dispatch to other machines (they will run however the config says, so can be multi jvm). I put the same args from build_cloud to build_cloud_with_hosts, to override the default config, just to be sure it's the same build_cloud as it would do for localhost (like on your laptop)
a couple tests I hadn't pushed also.
a couple of missing things around import h2o* in the last push
Minor change to have fine-grained control over HDFS options
Unwind broken GIT again, back to Inspect of this morning
update the ncaa rf test, make n0 up to date with list of tests to execute
Merge branch 'master' of github.com:0xdata/h2o
default JVM arguments deleted
Merge branch 'master' of https://github.com/0xdata/h2o
Cleanup the ipv4 sorting hack, remove redundant field

Should have the *proper* fix which is indeed an unsigned long compare
(and had been proposed as a fix earlier by Kevin, and yanked by me
and now added back by me)
updated to match cliff's update for s3 keys?
hopefully this is right for the latest
    s3Key= "s3://" + path + "/" + csvFilename
Merge branch 'master' of github.com:0xdata/h2o
adding deleting of the import* key in the loop, to get the importFolder or importS3 upload to happen again when we parseImport*
update test list
these were part of the delete key/source_key from parse stuff
oops typo
bettering reporting of elapsed time
Cleanup S3 loading

Remove googlish readFully & close-quietly, and be explicit about both of
these... in an effort to get cleaner stack traces.  Tighten the distance
between opening an S3 object and reading it, then closing it.  Add
comment to setRange about being *inclusive* (we're using classic
exclusive range set).
 Using HTTP s3 load by default
-1 S3 range fix