Thanks Hervé for documenting this, should be very useful. Do you think there's any merit in identifying if there are currently packages that take very close to the 40 minutes mark at the moment, and pointing this feature out to the maintainers directly? I don't know how tight for time the build process currently is.
Cheers, Mike On Thu, 5 Dec 2019 at 19:11, Pages, Herve <hpa...@fredhutch.org> wrote: > Hello developers, > > These builds were announced on this list in Nov. 2017 (see > https://stat.ethz.ch/pipermail/bioc-devel/2017-November/012326.html). > > The purpose of the "Long Tests builds" is to run tests that are too long > to run in the 40 min. allowed by the daily builds. With the Long Tests > builds, tests are allowed to run for a maximum of **6 hours** before a > TIMEOUT is raised. These builds are run once a week (every Saturday). > > Setting long tests in your package is easy and is now documented: > > https://bioconductor.org/developers/how-to/long-tests/ > > Also these builds are now running on all 3 platforms: > > https://bioconductor.org/checkResults/devel/bioc-longtests-LATEST/ > > Don't hesitate to use them! > > Questions/feedback 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: hpa...@fredhutch.org > Phone: (206) 667-5791 > Fax: (206) 667-1319 > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel