On 3 June 2025 at 15:36, Sebastian Meyer wrote:
| Am 03.06.25 um 13:22 schrieb Greg Hunt:
| > Dirk,
| > Even if he gets the test and example times to zero, his total time in that
| > thirteen minute run is still above ten minutes.  In my view the incomplete
| > time reporting (we don't know what makes up the thirteen minutes) is a bug
| > in the build process.
| 
| It is indeed unfortunate and perhaps a bug that the Windows check log 
| shows no runtime for

Oh I see.  Well I always took mine 'on another OS' as 'largely proportional'
which allowed me to, say, reduce overall test time by 50%.

It also helps that the testing framework I default to (tinytest, which I can
strongly recommend) defaults to showing test times so I generally have an
idea about relative 'cost' between different tests.

R itself adds timings to the test log but that is (arguably) rather hidden.
 
| > * checking whether package 'secr' can be installed ... OK
| 
| (which on the Debian check machine was reported with 164s)
| 
| as well as for the following checks of package loading
| (which takes relatively long for 'secr', even on Linux, ~5s each):
| 
| > * checking whether the package can be loaded ... OK
| > * checking whether the package can be loaded with stated dependencies ... OK
| > * checking whether the package can be unloaded cleanly ... OK
| > * checking whether the namespace can be loaded with stated dependencies ... 
OK
| > * checking whether the namespace can be unloaded cleanly ... OK
| > * checking loading without being on the library search path ... OK
| > * checking whether startup messages can be suppressed ... OK
| 
| Setting environment variable _R_CHECK_TIMINGS_=0 should reveal timings 
| for these checks. (Check option --as-cran only shows timings above 10s 
| by default.) I don't currently have a Windows machine at hand to test.

In general I think a policy of 'be more verbose' and 'have more generally
useful options on by default' would help.  This thread seems to show there
may be a need.

Cheers, Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Reply via email to