Hi Murray, On Tue, Jun 3, 2025 at 5:09 PM Murray Efford via R-package-devel <r-package-devel@r-project.org> wrote: > > 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 > I ran `R CMD check secr` on my Ubuntu machine and just the install took a couple minutes (on one core). That time isn't reported as a line item in the win-builder check log, but was close to half my total check time. You might not have noticed this if you use something like ccache.
For what it's worth, I'm running a Ryzen 7 3700X w/64GB of RAM that was otherwise mostly idle. Here's the command I ran, with a few of the reported timings for reference. #> time CCACHE_DISABLE=1 _R_CHECK_TIMINGS_=0 R CMD check secr_5.2.4.tar.gz * checking whether package 'secr' can be installed ... [152s/152s] OK ... * checking R code for possible problems ... [30s/30s] OK ... * checking re-building of vignette outputs ... [13s/13s] OK * checking PDF version of manual ... [9s/9s] OK ... real 5m23.509s user 4m57.181s sys 0m23.679s Obviously my machine isn't win-builder, but it does suggest installation is a big part of the total check time. Best, Josh > ________________________________ > 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 -- Joshua Ulrich | about.me/joshuaulrich FOSS Trading | www.fosstrading.com ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
