[R-pkg-devel] interpreting rhub platform failures

[Uwe Ligges]

The oputput is not helpful to identify the problem.

If it passes except for intel/rchk it could be some compiled code issue, 
but if you do not have such code, the issue is, if at all, in another 
package than yours.

noSuggest issues indicate you may be using a suggested package 
unconditionally?
If you are sure this is not the case in your code, go ahead and try 
CRAN. Although standard incoming checks won't check for the issues above.


Best,
Uwe Ligges





On 29.06.2025 22:14, smallepsilon wrote:
> I am preparing my R package for resubmission, and am using the "rhub" package to check it on various platforms. It passes the checks on all but three platforms (intel, nosuggests, and rchk), and I am hoping for guidance on how to interpret the failures.
> 
> The package initially failed on the "ubuntu-clang" platform, but it passed when I reran it without any changes. I tried rerunning the checks on intel, nosuggests, and rchk, but it failed again on each one.
> 
> The failure details are given below. Should I worry about these errors when I resubmit to CRAN?
> 
> - intel fails because of a problem loading "minqa", which is imported by "lme4", which my package suggests. The message reads:
> 
> Error in dyn.load(file, DLLpath = DLLpath, ...) :
>    unable to load shared object '/github/home/R/x86_64-pc-linux-gnu-library/4.6/minqa/libs/minqa.so':
>    libquadmath.so.0: cannot open shared object file: No such file or directory
> 
> I searched online for related errors, and found nothing about the intel platform from rhub specifically, but https://stackoverflow.com/questions/21149090/error-installing-minqa-in-r-3-0-2 leads me to think that it might be an issue beyond an rhub user's control.
> 
> - nosuggests fails because it cannot rebuild the vignettes. The error message is "there is no package called 'rmarkdown'", which is not surprising given that "rmarkdown" is suggested for building vignettes. I hope this is not a deal-breaker for CRAN....
> 
> - rchk fails for reasons that I cannot interpret. What I think is the relevant text is given below. My understanding is that this platform is used to test C/Fortran code included in a package, which mine does not use.
> 
> Run r-hub/actions/run-check using v1
> Run # If env var is not set, we run R CMD CHECK, otherwise the
> Run rchk.sh
> Installing package
> * installing *source* package ‘distfreereg’ ...
> ** this is package ‘distfreereg’ version ‘1.1’
> not using staged install with --libs-only
> ** using non-staged installation
> * DONE (distfreereg)
> Run # Fail for rchk errors.
> Fail for rchk errors
> Run # Save binary package
> Save binary package
> Could not find binary package.
> Run actions/upload-artifact using v4
> /usr/bin/docker exec  6bc8600b43794ccf106ebb57224b520f4df047df97d9876c1d815f10f15ffaf6 sh -c "cat /etc/*release | grep ^ID"
> Warning: No files were found with the provided path: check. No artifacts will be uploaded.
> 
> 
> Thanks for any help,
> 
> Jesse
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel