I am the author of R package animint which uses testthat for unit tests. This means that there is a single test file (animint/tests/testthat.R) and during R CMD check we will see the following output * checking tests ... Running ?testthat.R? I run these tests on Travis, which has a policy that if no output is received after 10 minutes, it will kill the check. Because animint's testthat tests take a total of over 10 minutes, Travis kills the R CMD check job before it has finished all the tests. This is a problem since we would like to run animint tests on Travis. One solution to this problem would be if R CMD check could output more lines other than just Running testthat.R. Can I give some command line switch to R CMD check or set some environment variable, so that some more verbose test output could be shown on R CMD check? [[alternative HTML version deleted]]
I really can't see it as a job for R to circumvent hare-brained sysadmin schemes like this.... You're not telling us who or what Travis is. I expect travis-ci.org has some clues, but in general, people on this list won't know. If it doesn't support setting parameters for the timeout, and it is anything Unix-like, can't you just set up a background process to echo a line every five minutes? As in (for i in 1 2 3 4 ; do sleep 10 ; echo "ping" ; done ) & R ; kill % (for larger values of 10, obviously; just showing the basic idea.) - Peter D. On 04 May 2015, at 17:52 , Toby Hocking <tdhock5 at gmail.com> wrote:> I am the author of R package animint which uses testthat for unit tests. > > This means that there is a single test file (animint/tests/testthat.R) and > during R CMD check we will see the following output > > * checking tests ... > Running ?testthat.R? > > I run these tests on Travis, which has a policy that if no output is > received after 10 minutes, it will kill the check. Because animint's > testthat tests take a total of over 10 minutes, Travis kills the R CMD > check job before it has finished all the tests. This is a problem since we > would like to run animint tests on Travis. > > One solution to this problem would be if R CMD check could output more > lines other than just Running testthat.R. Can I give some command line > switch to R CMD check or set some environment variable, so that some more > verbose test output could be shown on R CMD check? > > [[alternative HTML version deleted]] > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel-- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd.mes at cbs.dk Priv: PDalgd at gmail.com
If your tests can be divided into multiple files in the tests/ directory then you will get lines like * checking tests ... Running ?test1.R? Running ?test2.R? Running ?test3.R? ... Paul On 05/04/2015 11:52 AM, Toby Hocking wrote:> I am the author of R package animint which uses testthat for unit tests. > > This means that there is a single test file (animint/tests/testthat.R) and > during R CMD check we will see the following output > > * checking tests ... > Running ?testthat.R? > > I run these tests on Travis, which has a policy that if no output is > received after 10 minutes, it will kill the check. Because animint's > testthat tests take a total of over 10 minutes, Travis kills the R CMD > check job before it has finished all the tests. This is a problem since we > would like to run animint tests on Travis. > > One solution to this problem would be if R CMD check could output more > lines other than just Running testthat.R. Can I give some command line > switch to R CMD check or set some environment variable, so that some more > verbose test output could be shown on R CMD check? > > [[alternative HTML version deleted]] > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel >