go back to setting delete_keys_at_teardown (between tests) on the testdir_release four_hour_cloud.py o (i'm not sure if something at different level in the tests was setting this or not, but was seeing cases where a test would fail on a cloud, leaving the key locked, and then the next test using the same key name would fail). I suppose a more interesting thing would be to just unlock all keys at the beginning of a test on an existing clouds, since we should always be able to overwrite a corrupt existing key, without having to remove it? But we also want to avoid causing spills, so I guess I'll go back to this strategy (only affects the mr-0xb4 jenkins jobs that do multiple tests on a single cloud)
Merge branch 'master' of github.com:0xdata/h2o
these two tests accidently included the response col # in the ignored_cols list to GLM2, which used to be okay apparently..caused stack trace in latest GLM which tomas is fixing to be illegal argument exception. Updating these tests to not include response in ignored_cols (which would have been the original intent)