> Ben Bolker
> on Tue, 13 Oct 2020 12:46:11 -0400 writes:
>Following up on my questions from yesterday:
>I've been advised to (drastically) reduce the checking
> time of my package on CRAN's Windows platform (currently
> at 23 min). I've gone through and added
FWIW, we dealt with the tests-taking-too-long problem for CVXR (which
has a lot of tests) by mercilessly cutting out all tests on CRAN
(testthat::skip_on_cran()) except for some fundamental ones on atoms,
curvature, etc. We then rely on Github actions (with NOT_CRAN = true)
to run the full tes
Following up on my questions from yesterday:
I've been advised to (drastically) reduce the checking time of my
package on CRAN's Windows platform (currently at 23 min). I've gone
through and added a lot of conditionals to skip tests on CRAN. I could
reduce it farther but I'm starting to
