-
Notifications
You must be signed in to change notification settings - Fork 56
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
Error in pak without message during r-lib/actions/setup-r-dependencies@v2
#613
Comments
That's a EDCimport build failure, try adding
to see the real error. |
Thanks Gabor, I'm always amazed how you always answer so quickly 💪 I re-ran with
However, the reason being "there is no package called ‘xtable’" is surprising, as |
It is not a dependency of EDCimport:
|
Sorry, I am not sure I understand your point. I agree with the output of The only "special" thing I'm doing is |
Nevermind, I had some imports of flextable in NAMESPACE while flextable is only in Suggests! Maybe the error message could have been a bit more helpful though. Don't hesitate to close this issue if you think this is out of |
How would you implement a better error message if the error happens when building a dependency? |
I was thinking about a function that would check that every package engaged in NAMESPACE (import, importFrom, etc) is mentioned in Imports in DESCRIPTION. |
It makes sense to make installation more resilient. But there are a lot of things that have higher priority than checking if the packages we are installing are broken. |
I have a confusingly similar issue.
I am now bit by bit retesting old action runs, and now even merges which passed checks successfully before fail now. I don't know why, and I have basically no idea how to resolve this. I have tagged all commits which merge to There are a variety of things that confuse me here:
What confuses me most is that most of these tagged commits did pass at one point or another. And most of them have never been tested since, up until today - where they all fail. The state of the package did not change on most of these commits (some branches were force-pushed over again to rectify sudden bugs. However, this problem also manifests in commits prior to any force-pushing.) For ref: R CMD CHECK Overview. All of this is to say that I have very little clues as to what is actually going on, going wrong, or how to rectify this. Could someone help me figure out what the frick is going on here? Thank you. |
@Claudius-Appel imager does not work on Windows, on R 4.4.0: https://cran.rstudio.com/web/checks/check_results_imager.html |
Huh, that is weird, for several reasons. For one, I can compile my stuff flawlessly on my local machine. But that's only circumstantially relevant, I think. non-failing ref-workflow on |
You use a different repo setup for the two builds, CRAN has a binary for imager, PPPM does not. |
@gaborcsardi Well, thank you. I don't think I would have nailed that down ._. Which means that in both cases |
I feel silly for not noticing that. However, it works now. Again, thank you for your support on this. |
Hi,
I'm using pkgdown.yaml to build the documentation website for a package of mine.
During the process,
r-lib/actions/setup-r-dependencies@v2
usespak
to install dependencies and then build the package.This very last step throws an error, but the error message is only "Failed to build the package", with no further information.
Here is some context of the error (see the run for the whole log):
If you look at the runs, you'll see this GHA failed a lot but it is only because I was lazy about
_pkgdown.yml
, up until "clinical utils (WIP)".Starting at "Update waterfall_plot.Rd", the error is the one above.
What is surprising is that the commit of "Update waterfall_plot.Rd" is very minor, so I don't think it could explain this error.
Thanks for your help!
The text was updated successfully, but these errors were encountered: