Thanks to Dirk, Greg and Seb for grappling with this. The comments give me confidence to appeal to CRAN to wave this through as it stands - I think Uwe has obliged in the past, but I would rather not rely on that. More complete reporting of check times would be welcome. Murray ________________________________ From: Dirk Eddelbuettel <e...@debian.org> Sent: Wednesday, 4 June 2025 02:33 To: Greg Hunt <g...@firmansyah.com> Cc: Dirk Eddelbuettel <e...@debian.org>; Murray Efford <murray.eff...@otago.ac.nz>; R Package Development <r-package-devel@r-project.org> Subject: Re: [R-pkg-devel] Check time > 10min
Greg, On 4 June 2025 at 00:19, Greg Hunt wrote: | In the original email, there was this: | | * checking examples ... [87s] OK | * checking tests ... [59s] OK | | Am I interpreting it wrong or are these numbers the elapsed times for checking | examples and tests? If you follow the URL from the original post [1] you will see that it links to a (Windows) check result ending in 'Status: OK'. No issue here. Murray's original post also said '[it[ fails CRAN pre-test on Windows (R 4.5.0) because total check time exceeds 10 min (it's 760 seconds or 13 min)'. So we are talking about two different checks. As Seb alluded to, it is unfortunate that the (failing) pre-check test does not give timings (whereas the one you refer to does, but it did not fail). Hth, and feel free to hit me up off list with follow-ups as we may have gone on long enough on list. Cheers, Dirk [1] https://win-builder.r-project.org/incoming_pretest/secr_5.2.2_20250602_054847/Windows/00check.log<https://win-builder.r-project.org/incoming_pretest/secr_5.2.2_20250602_054847/Windows/00check.log> -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
