-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Active? #7
Comments
I'm curious about this too. I see that it's still Travis CI-oriented, which now seems out of date ... ? I've been using revdepcheck on a local(ish) server (and painfully going through all the bits of installation necessary ...) I certainly wouldn't mind a better solution! Some very unstructured notes of the kinds of stuff I've done to get system dependencies working: |
I have left it aside for a few years but I did hope to resurrect it at some point. Since I've got two votes and I need to use this myself from time to time, I'll probably start the work in the next few days. I'll definitely retire Travis and switch to Github actions. The latter allows 5Gb of cache and 6 hours of running time. These limits are much better than Travis. Previously one of my main challenges in this project was Travis's 40 or perhaps 50 minutes timeout. Six hours is probably enough even for knitr to finish checking its reverse dependencies. I'll keep you posted. |
I've mostly finished the transition from Travis to Github action now. Please see the updated readme of this repo. @therneau Unfortunately your survival package is unlikely to finish rev checks in six hours: https://github.com/yihui/crandalf/actions/runs/628783882 I mentioned two possible workarounds in readme: https://github.com/yihui/crandalf#timeout I think I know a better way to solve this problem, but I'm running out of time now. |
I've updated readme for the case of large numbers of reverse dependencies: https://github.com/yihui/crandalf#timeout Now you can use crandalf to check any numbers of packages (and of course, you'll have to wait quite a while for the checks to finish). |
Is this site still active? I see no requests in a long while.
The text was updated successfully, but these errors were encountered: