Closed kkmann closed 2 years ago
alternatively, just removing the explicit call to ´devtools::test´ would also do the trick. my understanding is that ´R CMD check´ runs the tests anyhow
currently, some of the multicore tests seem to fail. Note that - Rscript -e 'devtools::test()'
will not lead to a failed CI build even if there are tests failing, is that intended?
the relevant section in the docs is here: https://docs.travis-ci.com/user/languages/r/#customizing-the-travis-build-steps
Now using github actions instead of travis
I think the current setup does not honestly report the results of R CMD CHECK because you call devtools::test afterwards and Travis does not use bash strict mode by default (i.e. currently 'checks passed' only means that the tests run through, but not the full check).
See also https://github.com/travis-ci/travis-ci/issues/1066
I think a line
- set -e
would be needed but that depends a bit on the intended behaviour.