-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
avoid warning when missing R cache dir #1129
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1129 +/- ##
=======================================
Coverage 92.35% 92.35%
=======================================
Files 46 46
Lines 2654 2654
=======================================
Hits 2451 2451
Misses 203 203 |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if 8f839e6 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
In my understanding, a warning is given if the path does not exist. Also, in the help file, searching for writ does not give any results. So is it non-existant or non-writable? |
I think non-extant because non-writable. |
Really? Or the other way round? |
@MichaelChirico happy to help here, can you catch up? |
Sure, what else would you like to see in the PR before merge? |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if c38d7f9 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
I don’t understand that. Can you explain? |
i.e. the process doesn't have permission to write to that directory, so it can't create the expected file(s). |
Ok thanks. @IndrajeetPatil seems link rot check not working anymore. Can you habe a look? |
We have a strange setup where
tools::R_user_dir()
won't be writeable during testing, sonormalizePath()
throws a warning here. The code works as expected after the warning (cache is just deactivated), so settingmustWork=FALSE
here seems reasonable.OTOH, this might be pretty unique to our testing systems, so if it's too niche an issue we'll just maintain this patch in our fork.