* using log directory ‘/srv/hornik/tmp/CRAN/timeplyr.Rcheck’
* using R Under development (unstable) (2023-10-09 r85295)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 16.0.6 (15)
    GNU Fortran (Debian 13.2.0-4) 13.2.0
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘timeplyr/DESCRIPTION’ ... OK
* this is package ‘timeplyr’ version ‘0.2.0’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [3s/4s] NOTE
Maintainer: ‘Nick Christofides <nick.christofides.r@gmail.com>’

New submission
* 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 ‘timeplyr’ can be installed ... [26s/26s] OK
* used C++ compiler: ‘Debian clang version 16.0.6 (15)’
* 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 R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [1s/1s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/0s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the namespace can be unloaded cleanly ... [1s/1s] OK
* checking loading without being on the library search path ... [1s/1s] OK
* checking whether startup messages can be suppressed ... [1s/1s] OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... NOTE
Mismatches for apparent methods not registered:
rep:
  function(x, ...)
rep.int.yearqtr:
  function(x, times)

rep:
  function(x, ...)
rep.int.yearmon:
  function(x, times)
See section ‘Registering S3 methods’ in the ‘Writing R Extensions’
manual.
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [14s/14s] OK
* checking Rd files ... [0s/0s] OK
* checking Rd metadata ... OK
* checking Rd line widths ... 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 compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [47s/20s] NOTE
Examples with CPU (user + system) or elapsed time > 5s
             user system elapsed
time_expand 5.794  0.143   1.454
Examples with CPU time > 2.5 times elapsed time
                user system elapsed  ratio
roll_na_fill   2.255  0.163   0.151 16.013
q_summarise    3.592  0.113   0.282 13.138
fskim          3.117  0.193   0.285 11.614
time_count     4.061  0.156   0.698  6.042
get_time_delay 4.105  0.064   0.762  5.471
time_expand    5.794  0.143   1.454  4.083
fexpand        3.418  0.088   1.299  2.699
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ... [242s/54s] NOTE
  Running ‘testthat.R’ [242s/54s]
Running R code in ‘testthat.R’ had CPU time 4.5 times elapsed time
* checking PDF version of manual ... [4s/4s] OK
* checking HTML version of manual ... [2s/2s] OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 4 NOTEs