* using log directory 'd:/Rcompile/CRANpkg/local/4.6/QoLMiss.Rcheck'
* using R version 4.6.1 (2026-06-24 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
* current time: 2026-08-12 08:50:43 UTC
* checking for file 'QoLMiss/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'QoLMiss' version '0.1.0'
* package encoding: UTF-8
* 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 'QoLMiss' can be installed ... OK
* 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 ... [7s] 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 contents of 'data' directory ... OK
* checking data for non-ASCII characters ... [0s] OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking examples ... [7s] OK
* checking PDF version of manual ... [20s] OK
* checking HTML version of manual ... [8s] 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:
91   50.00000   0.00000 25.000000   0.00000  77.77778
92   33.33333   0.00000 25.000000 100.00000  66.66667
93   50.00000  33.33333 41.666667   0.00000  77.77778
94   16.66667   0.00000 25.000000 100.00000  77.77778
95   50.00000   0.00000 16.666667   0.00000  44.44444
96   33.33333 100.00000 41.666667  66.66667  77.77778
97   50.00000  66.66667 25.000000 100.00000  77.77778
98   16.66667  33.33333 33.333333 100.00000  44.44444
99   33.33333  66.66667 50.000000   0.00000  44.44444
100  33.33333   0.00000 66.666667  66.66667  66.66667
> ##
> 
> 
> 
> 
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed:  5.96 0.31 6.28 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 ?) ========