futureverse / future.apply

:rocket: R package: future.apply - Apply Function to Elements in Parallel using Futures
https://future.apply.futureverse.org
211 stars 16 forks source link

CRAN submission: Found the following files/directories: 'Rscript2af8ccbfb3f34' 'Rscript92e8cbfb3f24' #104

Closed HenrikBengtsson closed 2 years ago

HenrikBengtsson commented 2 years ago
* using log directory 'd:/RCompile/CRANincoming/R-devel/future.apply.Rcheck'
* using R Under development (unstable) (2022-09-06 r82818 ucrt)
* using platform: x86_64-w64-mingw32 (64-bit)
* using session charset: UTF-8
* checking for file 'future.apply/DESCRIPTION' ... OK
* this is package 'future.apply' version '1.9.1'
* checking CRAN incoming feasibility ... [15s] Note_to_CRAN_maintainers
Maintainer: 'Henrik Bengtsson <henrikb@braju.com>'
* 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 serialization versions ... OK
* checking whether package 'future.apply' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking 'build' 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 R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [1s] OK
* checking whether the package can be loaded with stated dependencies ... [0s] OK
* checking whether the package can be unloaded cleanly ... [1s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s] OK
* checking whether the namespace can be unloaded cleanly ... [1s] OK
* checking loading without being on the library search path ... [1s] 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 ... [9s] OK
* checking Rd files ... [1s] 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 installed files from 'inst/doc' ... OK
* checking files in 'vignettes' ... OK
* checking examples ... [3s] OK
* checking for unstated dependencies in 'tests' ... OK
* checking tests ... [160s] OK
  Running 'fold.R' [9s]
  Running 'future_apply.R' [7s]
  Running 'future_by.R' [6s]
  Running 'future_eapply.R' [3s]
  Running 'future_lapply,RNG.R' [27s]
  Running 'future_lapply,globals.R' [7s]
  Running 'future_lapply.R' [20s]
  Running 'future_mapply,globals.R' [4s]
  Running 'future_mapply.R' [11s]
  Running 'future_replicate.R' [4s]
  Running 'future_sapply.R' [29s]
  Running 'future_tapply.R' [2s]
  Running 'future_vapply.R' [11s]
  Running 'globals,tricky_recursive.R' [3s]
  Running 'rng.R' [1s]
  Running 'stdout.R' [14s]
  Running 'utils.R' [1s]
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in 'inst/doc' ... OK
* checking re-building of vignette outputs ... [3s] OK
* checking PDF version of manual ... [23s] OK
* checking HTML version of manual ... [3s] OK
* checking for detritus in the temp directory ... NOTE
Found the following files/directories:
  'Rscript2af8ccbfb3f34' 'Rscript92e8cbfb3f24'
* DONE
Status: 1 NOTE
HenrikBengtsson commented 2 years ago

This seems like a hiccup, or at least sporadic. I cannot reproduce it with win-builder-devel (tried twice). I also cannot reproduce it with R-devel on a Windows 10 VM (tried 2-3 times). Resubmitting the exact same tarball to CRAN passed without this problem.