rhub

rhub copied to clipboard

The configurations of r-hub's server farm do not seem to mention the BLAS implemtations used. CRAN seems to have started to use different BLAS implementions or at least additional checks so I believe it is worthwhile to a) mention what r-hub offers and b) even offer various BLAS implementations on r-hub.

But maybe I did not find the right spot in the documentation?

R-hub uses the platform and R default, everywhere.

We could have an extra one, maybe. Do you have particular suggestions? What does CRAN use for their extra checks?

r-devel-linux-x86_64-debian-gcc started to use OpenBLAS (we were notified as an error was caused by numerical precision diversion), but it is not documented as far as I can see. And I don't know if they plan to continue to use OpenBLAS for this platform's test.

There seem to be additional checks on CRAN (at least for some packages, see e.g. data.table) with various BLASes: https://cran.rstudio.com/web/checks/check_issue_kinds.html

I randomly found the R Journal article mentioning the change "The package check pages now also show issues found by checks with alternative BLAS/LAPACK implementations (ATLAS, MKL and OpenBLAS), provided by Brian D. Ripley (see https://www.stats.ox.ac.uk/pub/bdr/Rblas/README.txt for more information)."

Some of the packages have now received strikes from CRAN, because they don't pass some of the checks on ATLAS / MKL. So, it would help a lot to package maintainers if there were additional checks on rhub to include those different versions of BLAS.

Seconded. It would be tremendously helpful (and would alleviate work for the CRAN maintainers) to be able to test against the MKL configuration used for CRAN checks. Here is the description of the builds: https://www.stats.ox.ac.uk/pub/bdr/Rblas/README.txt

I am afraid that we cannot legally publish a Docker container with MKL. But I am not entirely sure.

We had a floating point precision issue that only shows up on CRAN checks with ATLAS. We tried to fix it by adjusting the tolerance in expect_equal() but we have no way to verify this is sufficient before pushing it to CRAN.

A rhub platform would be amazing :+1:!

In the same idea, I found today the list of additional issues with this list of complementary tests: If you click on additional issues on this page: https://cran.r-project.org/web/checks/check_results_gitdown.html, you will find the list above: https://cran.r-project.org/web/checks/check_issue_kinds.html (until I submit a new version)

In case it is useful, details lead to README pages from some of these directories: https://www.stats.ox.ac.uk/pub/bdr/

@Bisaloo I also got some floating point precision problems. I decided to transform values into text for unit tests (dates in my case).

This issue is about the previous R-hub system, it does not apply to the new system, so I am closing it now. Please see https://r-hub.github.io/rhub/ for the new system, R-hub v2.