* using log directory 'd:/Rcompile/CRANpkg/local/4.6/polywog.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 19:39:43 UTC
* checking for file 'polywog/DESCRIPTION' ... OK
* this is package 'polywog' version '0.4-2'
* 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 'polywog' can be installed ... OK
* used C++ compiler: 'g++.exe (GCC) 14.3.0'
* 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 line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compiled code ... OK
* checking examples ... [8s] OK
* checking PDF version of manual ... [26s] OK
* checking HTML version of manual ... [7s] 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:
3   8.511111 39.61437 38.13406 41.91244
4   9.576667 42.42179 41.21005 43.78592
5  10.642222 45.47120 44.26933 47.39811
6  11.707778 48.76258 47.16804 51.35492
7  12.773333 52.29594 49.86878 55.55761
8  13.838889 56.07127 52.42509 60.00617
9  14.904444 60.08858 55.20005 64.70061
10 15.970000 64.34787 58.19367 70.24828
> 
> ## Plotting
> pred_income <- predVals(fit1, "income", n = 10)
> plot(pred_income)
> 
> 
> 
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed:  7.36 0.36 7.75 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 ?) ========