[Bioc-devel] "Long tests" builds

[Hervé Pagès]

Hi developers,

In this recent thread:

   https://stat.ethz.ch/pipermail/bioc-devel/2017-October/012154.html

some of you expressed the desire to be able to have extra/longer unit
tests in their package, with these tests being run on a regular basis
by our build machines.

To address this, we've started the "long tests" builds:

   https://bioconductor.org/checkResults/

Any software package can participate to these builds. To participate
you need to:

   1) Subscribe your package.
      To subscribe, add a .BBSoptions file to the top-level folder of
      your package source tree with the following line in it:

      RunLongtests: TRUE

   2) Create the longtests/ folder in the top-level folder of your
      package source tree and put tests in it, just like you would
      do with the tests/ folder.

The "long tests" builds will run 'R CMD check --test-dir=longtests'
once a week (every Saturday) and thus will run the tests located in
the longtests/ folder. The results will get published here:

   https://bioconductor.org/checkResults/3.7/bioc-longtests-LATEST/

The maximum allowed time for the tests to complete is 6h. If they
take more, they get interrupted and a TIMEOUT is reported. Keep in
mind that 'R CMD check' is run with the --force-multiarch option on
Windows. This means that tests are executed twice on this platform,
once with R running in 32-bit mode, and once with R running in 64-bit
mode. The 6h limit is for the total time of the 'R CMD check' command.

Just to clarify, the daily software packages aren't changed: they
still run the tests located in the tests/ folder and the TIMEOUT
limit is still 40 min.

Feedback/questions/comments are welcome.

Cheers,
H.

-- 
Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpages at fredhutch.org
Phone:  (206) 667-5791
Fax:    (206) 667-1319