-
Notifications
You must be signed in to change notification settings - Fork 758
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
devtools::check() is slow #2323
Comments
Thanks for opening this issue! We are tracking this in r-lib/rcmdcheck#90 and r-lib/pkgbuild#59. However it is really due to the behavior of I am not sure it is possible to write without breaking backwards compatibility, and I have doubts on R core accepting it, which is why no one has undertaken it to this date. I would suggest you move directories with lots of files outside the package directory. |
Thanks for pointing me to the existing open issues and sorry having created a new one for that. Wasn't aware of them. Unfortunately, it is not possible for me to move the .git directory nor to change the lib path. Will have to wait until a solution is available, and meanwhile run less checks. Maybe I will start writing my own |
FYI, did write such function (okay, maybe not perfect) to check the project much faster, by first copying the files to a
The good thing about this approach is:
Maybe a good idea to include this in The bad thing: it is fast, but can even be faster I then wrote a shell script to perform the same, but using
The good thing: it's really fast The bad thing: Enjoy |
The
preparing
step indevtools::check()
is very slow. It takes about 5 minutes.─ preparing '[my-package-name]': (5m 42.6s)
I noticed that removing directories with lots of files like
.git
helps, but this is not very practical. My package manager is also installing files in the project directory, so I guess this is also slowing down.Is there a way to speed this up? I looked into the documentation and I tried using the
.Rbuildignore
but it does not ignore the files during this step.The text was updated successfully, but these errors were encountered: