Regression 3060 fails on GLRM in R tests

[exalate-issue-sync[bot]]

runit_glrm_benign.R runit_glrm_arrests.R

Regression branch versus latest Nightly, possibly a breaking change happened.

Appears Safe Rest calls are failing

http://172.16.2.161:8080/view/Regression/job/h2o_regression_runit_small/55/artifact/h2o-r/tests/results/testdir_algos_glrm_runit_glrm_benign.R.out.txt

http://172.16.2.161:8080/view/Regression/job/h2o_regression_runit_small/55/artifact/h2o-r/tests/results/testdir_algos_glrm_runit_glrm_arrests.R.out.txt

[exalate-issue-sync[bot]]

Raymond Peck commented: If it can't be fixed quickly please NOPASS this so we can get clean results for the release. Thanks!

[exalate-issue-sync[bot]]

Former user commented: I changed the name of an input parameter. You need to manually remove the h2o R package and reinstall it for the changes to take place. Just sourcing the R code does not work.

[exalate-issue-sync[bot]]

Raymond Peck commented: Since we're considering this a bugfix Anqi has approval to make this breaking change. She's going to:

0. Move the endpoints and schemas for PCA, GLRM and SVD to /99 to indicate that they're still in flux. The R and Python clients and Flow ([~accountid:557058:8865629f-3e0a-4948-abde-e994a0051a8e]) will need to be tweaked to call /99.

All the tests in master must pass after this.

1. Make the client changes in the REST_API_REGRESSION_V3 branch.

All the tests in the regression job must pass after this.

[exalate-issue-sync[bot]]

Prithvi Prabhu commented: Flow 0.3.27 has the endpoint related changes.

[DinukaH2O]

JIRA Issue Migration Info

Jira Issue: PUBDEV-1581 Assignee: Former user Reporter: Jeff Gambera State: Resolved Fix Version: N/A Attachments: N/A Development PRs: N/A