• using R Under development (unstable) (2024-04-14 r86421)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 18.1.0 (rc4-1)     Debian flang-new version 18.1.0 (rc4-1)
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘ATAforecasting/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘ATAforecasting’ version ‘0.0.60’
• 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 executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘ATAforecasting’ can be installed ... OK See the install log for details.
• used C compiler: ‘Debian clang version 18.1.0 (rc4-1)’
• used C++ compiler: ‘Debian clang version 18.1.0 (rc4-1)’
• checking package directory ... OK
• checking for future file timestamps ... 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 ... [7s/10s] OK
• checking whether the package can be loaded with stated dependencies ... [6s/8s] OK
• checking whether the package can be unloaded cleanly ... [6s/8s] OK
• checking whether the namespace can be loaded with stated dependencies ... [6s/8s] OK
• checking whether the namespace can be unloaded cleanly ... [7s/8s] OK
• checking loading without being on the library search path ... [7s/8s] OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... NOTE Fortran STOP IEEE arithmetic exceptions signaled: INEXACT
• checking S3 generic/method consistency ... WARNING Fortran STOP IEEE arithmetic exceptions signaled: INEXACT See section ‘Generic functions and methods’ in the ‘Writing R Extensions’ manual.
• checking replacement functions ... WARNING Fortran STOP IEEE arithmetic exceptions signaled: INEXACT The argument of a replacement function which corresponds to the right hand side must be named ‘value’.
• checking foreign function calls ... NOTE Fortran STOP IEEE arithmetic exceptions signaled: INEXACT See chapter ‘System and foreign language interfaces’ in the ‘Writing R Extensions’ manual.
• checking R code for possible problems ... [50s/58s] NOTE Fortran STOP IEEE arithmetic exceptions signaled: INEXACT Fortran STOP IEEE arithmetic exceptions signaled: INEXACT Fortran STOP IEEE arithmetic exceptions signaled: INEXACT
• checking Rd files ... [8s/10s] WARNING Fortran STOP IEEE arithmetic exceptions signaled: INEXACT
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... WARNING Fortran STOP IEEE arithmetic exceptions signaled: INEXACT All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual.
• checking for code/documentation mismatches ... WARNING Fortran STOP IEEE arithmetic exceptions signaled: INEXACT Fortran STOP IEEE arithmetic exceptions signaled: INEXACT Fortran STOP IEEE arithmetic exceptions signaled: INEXACT
• checking Rd \usage sections ... NOTE Fortran STOP IEEE arithmetic exceptions signaled: INEXACT The \usage entries for S3 methods should use the \method markup and not their full name. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual.
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... [0s/0s] OK
• checking LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking compilation flags in Makevars ... OK
• checking for GNU extensions in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking use of PKG_*FLAGS in Makefiles ... OK
• checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking examples ... [14s/17s] OK Examples with CPU (user + system) or elapsed time > 5s               user system elapsed ATA.Accuracy 5.258 0.114 6.707
• checking PDF version of manual ... [7s/9s] OK
• checking HTML version of manual ... [2s/3s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 5 WARNINGs, 4 NOTEs