The page you have listed is for long tests. If long tests are implemented through the documented process, those checks have 40 minutes to run and are currently only run once per week.
The daily builders do not give such a large time limit to packages. We build and check all packages so there is some restriction on how much and for how long packages utilizes resources. http://bioconductor.org/developers/package-guidelines/#correctness The requirements are currently set for 10 minutes as described in the above document. Some things to consider to help meet requirements. It is often only necessary to use a small subset of data for examples, tests, and vignette demonstrations rather than a full dataset. If it is do to extensive testing, consider implementing the long tests using the documentation you referenced. Cheers, Lori Shepherd Bioconductor Core Team Roswell Park Comprehensive Cancer Center Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263 ________________________________ From: Bioc-devel <bioc-devel-boun...@r-project.org> on behalf of migdal migdal <mcjmig...@gmail.com> Sent: Friday, February 12, 2021 12:54 PM To: bioc-devel@r-project.org <bioc-devel@r-project.org> Subject: [Bioc-devel] What is the Timeout limit on R CMD check? Dear all, I am currently in the process of submitting my package to Bioconductor and I got a bit stuck trying to go through the R CMD CHECK. The problem I am facing at the moment is TIMEOUT: R CMD check exceeded 14 mins (here is full report if needed http://secure-web.cisco.com/1kh4JitBMHEZDPJI2F4hhkQwxQNrx77h5PCnV5IJaiVDDcr1L-XKSAZZsT9bAGTf8ovtpMbz5ZlS7J2EHb-L-b3hoD9Q0uhcD3qFrDfCFUxnePuV0FdxsIOzLn5Ea_oFqbFc3rbC4TWbp2xdMK2qf8ycydsS7KHs0y5M2JiWLixx7YBTvK0aKn9zDIhWbhbuxqcPsBMH6nSMtdhp49dyCOoFs-QVbL97qWvBPkn09LYRIgRunOgpZlPEJiq3q5T7y5t4k7gNtTUYfZ3NMxt0jT3G0ZN4N8AZQlDQ0XrJLhxIhwH8OwYaCtEsasheAKY7B/http%3A%2F%2Fbioconductor.org%2Fspb_reports%2FmidasHLA_buildreport_20210210035124.html) While the message is obvious, it is unclear to me what is the time limit for R CMD CHECK? Such that I know what to aim at. I've found some information here https://secure-web.cisco.com/1c42NFVNw_hnn314vs3Jn4VQY1Hi6JMrwbrwHtHZvq10T5XczX3OtMPgHIj0NELOUcyiBeQvFyUD4CfDnSZt0nCRkPzfafPH89ICjUadYnf5oSIqP2WlOLnLcUV46hy-8ngLLJg74MvOU1KyD8Eh8h2Nux7y-XRIxGneKYqPI4dvC7FrcbixLxRgSg_aXMwS1Qk4ccZu17SR6xe8eUbSjHB-4cmYQiR-nkwI_GCOYFVNRZ4BIHe4-CKWeyFIPHqSzoCplZmDal9KkuBAdaQzaX_3APYHvvlMHJn1pEMdaVlc_MHena0FNvbs9vObT57xy/https%3A%2F%2Fbioconductor.org%2Fdevelopers%2Fhow-to%2Flong-tests%2F, but it says: "The maximum amount of time that R CMD check is allowed to spend on each package is 40 min." Does not really add up with the TIMEOUT error above, unless I am missing something. Cheers Maciek [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://secure-web.cisco.com/13j4YK3YrEqvV_sshxQfPB8FFy9hXtijd9LRn_CY_G9rYOkImHzIsKGioVXBnLwGEykMZpyO1ciaejo4yo54rZtyibk2ypIl4gniELWd6I3lwFEhiaUCRFd7iWJESmpQTVZ56zGJEz9j-iBT9zNrLchwQAIYiAMXmr-ATJaTdkCm8dfRayu8Y2zKSEDuA69BDxNJB2JUQk7aTTFsMle9k6RovnV_rP8m0Za0domnxIfb3slINUToki6AXjfS2w95otK0vuGOS5LTgddRIK7xPUMehP_fXEF-JKu8T1vCsGQSJZBzQZ5gk2o1RkQQXbTm8/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you. [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
