* using log directory 'd:/Rcompile/CRANpkg/local/4.6/ARIMAANN.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 05:49:56 UTC
* checking for file 'ARIMAANN/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'ARIMAANN' 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 'ARIMAANN' 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 ... [3s] 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 ... [0s] 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 ... [3s] OK
* checking PDF version of manual ... [19s] OK
* checking HTML version of manual ... [1s] 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:
 [92] 1804.1907 3025.4198 3438.7293 1902.8765 2373.1370 3096.5269 1078.3772
 [99]  620.6967  337.1962  742.4174  892.5710 1108.0234 1969.9418 2989.9039
[106] 3480.8800 1934.5151  771.6426  320.8543  932.5790 1049.6378 1496.4668
[113] 2050.8869 2919.6620

$forecasted.values
Time Series:
Start = 1935 
End = 1939 
Frequency = 1 
[1] 3072.4169 2175.2473 1389.0605  937.9848  862.3349

> 
> 
> 
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed:  2.23 0.28 2.52 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 ?) ========