-
Notifications
You must be signed in to change notification settings - Fork 32
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
Run tests with a readonly library on CRAN #221
Conversation
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.
We can expedite this if the CRAN team reaches out.
wrong directory, copy-paste from solution
eb87e7e
to
b8c5656
Compare
7ab3a4b
to
018c8de
Compare
a8ac5bf
to
018c8de
Compare
@martinstuder tried to do a check for files added to the library after installation, but there is no option to do this with the R check action, and the action itself either cleans up or uses its own R lib. I checked locally on multiple machines, that should suffice. |
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.
lgtm
There is a new CRAN check, running the package check with a readonly R library.
See https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/XLConnect-00check.html and https://github.com/kalibera/cran-checks/tree/master/rlibro/results/XLConnect.
→ Avoid any writes in the non-FULL case, including writing the unit tests results.