-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests for R binaries and packages #23
Conversation
@@ -8,7 +8,7 @@ if [ ! -f ${PKG_FILE} ]; then | |||
exit 0 | |||
fi | |||
|
|||
zypper --non-interactive install ${PKG_FILE} | |||
zypper --non-interactive --no-gpg-checks install ${PKG_FILE} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, this brings up an interesting question -- should we start signing our installers? Jenkins is already configured with the secrets we need for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think that'd be great. We still have this issue open: #7
0bbc7cb
to
5fe168b
Compare
Closing - I've redone this and will open a new PR |
These are tests to help verify that the R binaries are configured/compiled properly, and that the R packages work.
Specifically, this installs the R deb/rpm in a base OS container, runs some R tests, and uninstalls the deb/rpm. The R tests were copied from https://github.com/rstudio/r-docker, but I only pulled in the tests relevant to r-builds (e.g. BLAS is configured properly, no missing runtime libraries, help pages work).
To test locally, first build the R packages:
And then run the tests: