• using R version 4.5.3 (2026-03-11 ucrt)
• using platform: x86_64-w64-mingw32
• R was compiled by     gcc.exe (GCC) 14.3.0     GNU Fortran (GCC) 14.3.0
• running under: Windows Server 2022 x64 (build 20348)
• using session charset: UTF-8
• checking for file 'gamlss.lasso/DESCRIPTION' ... OK
• this is package 'gamlss.lasso' version '1.0-1'
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking whether package 'gamlss.lasso' can be installed ... OK See the install log for details.
• checking installed package size ... OK
• checking package directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [2s] OK
• checking whether the package can be loaded with stated dependencies ... [2s] OK
• checking whether the package can be unloaded cleanly ... [2s] OK
• checking whether the namespace can be loaded with stated dependencies ... [2s] OK
• checking whether the namespace can be unloaded cleanly ... [2s] OK
• checking loading without being on the library search path ... [2s] OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [6s] OK
• checking Rd files ... [1s] OK
• checking Rd metadata ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking examples ... [9s] OK
• checking PDF version of manual ... [19s] OK
• checking HTML version of manual ... [2s] OK
• DONE Status: OK Check process probably crashed or hung up for 20 minutes ... killed Most likely this happened in the example checks (?), if not, ignore the following last lines of example output: true 0.30000000 0 0 0 0 0 0 0.3000000 0 0 0 0 0 0 0 0 estimate 0.08994491 0 0 0 0 0 0 0.1997212 0 0 0 0 0 0 0 0          V17 V18 V19 V20 V21 V22 V23 V24 V25 V26 V27 V28 V29 V30 V31 V32 true 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.3000000 0 estimate 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.1657854 0          V33 V34 V35 V36 V37 V38 V39 V40 V41 V42 V43 V44 V45 V46 V47 V48 true 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.3000000 estimate 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.1437099                V49 V50 true 0.3000000 0 estimate 0.1468432 0 > > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 7.58 0.85 8.44 NA NA > grDevices::dev.off() null device           1 > ### > ### Local variables: *** > ### mode: outline-minor *** > ### outline-regexp: "\\(> \\)?### [*]+" *** > ### End: *** > quit('no') ======== End of example output (where/before crash/hang up occured ?) ========