Check results for 'RDieHarder'

using R version 4.3.1 (2023-06-16)
using platform: aarch64-apple-darwin20 (64-bit)
R was compiled by Apple clang version 14.0.0 (clang-1400.0.29.202) GNU Fortran (GCC) 12.2.0
running under: macOS Ventura 13.4
using session charset: UTF-8
checking for file ‘RDieHarder/DESCRIPTION’ ... OK
this is package ‘RDieHarder’ version ‘0.2.6’
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 ‘RDieHarder’ can be installed ... [12s/15s] OK See the install log for details.
used C compiler: ‘Apple clang version 14.0.0 (clang-1400.0.29.202)’
used SDK: ‘MacOSX11.3.sdk’
checking installed package size ... OK
checking package directory ... 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 ... [0s/0s] 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 ... [0s/0s] OK
checking loading without being on the library search path ... [0s/0s] OK
checking startup messages can be suppressed ... [0s/0s] 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 ... [1s/1s] OK
checking Rd files ... [0s/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 line endings in shell scripts ... 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 include directives in Makefiles ... OK
checking compiled code ... OK
checking sizes of PDF files under ‘inst/doc’ ... OK
checking installed files from ‘inst/doc’ ... OK
checking files in ‘vignettes’ ... OK
checking examples ... [0s/0s] OK
checking for unstated dependencies in ‘tests’ ... OK
checking tests ... [0s/0s] OK Running ‘RDieHarder.R’ [0s/0s] Comparing ‘RDieHarder.Rout’ to ‘RDieHarder.Rout.save’ ...7,72d6 < < dieharder version 3.31.1 Copyright 2003 Robert G. Brown < < Usage: < dieharder [-a] [-b bits] [-d diehard test number] [-f filename] < [-g generator number] [-h] [-i iterations] [-l] < [-n ntuple] [-p number of p samples] [-q] [-o filename] < [-N] [-r rgb test number] [-s sts test number] < [-t number of test samples] [-u user test number] < [-v verbose flag] [-x xvalue] [-y yvalue] [-z zvalue] < < -a Runs all the tests with standard/default options to create a report < -b bits - sets the number of bits to be used in tests that act on a bit < string of variable length, e.g. the rgb bitdist test. < -d test number - selects specific diehard test. < -f filename - two generators permit either formatted ASCII numbers < or raw binary numbers to be read in from a file for testing. < Note well that some (default) tests require 10,000,000 or more rands! < To see a sample of the (required) header for ASCII formatted input, run < < dieharder -o -f example.input -t 10 < < and then examine the contents of example.input. < Raw binary input reads 32 bit increments of the specified data stream. < -g generator number - selects a specific generator for testing. Using < -1 causes all known generators to be printed out to the display. < -h prints context-sensitive help -- usually Usage (this message) or a < test synopsis if entered as e.g. dieharder -d 3 -h. < -i iterations - sets iteration count for timing runs (should not be < needed). < -l list all known tests. < -n ntuple - set ntuple length for tests on short bit strings that permit < the length to be varied (e.g. rgb bitdist). < -o filename - output -t count random numbers to file. < -N force the usage of non-overlapping samples in certain diehard tests. < -p count - sets the number of p-value samples per test (default 100). < -q selects "quiet" operation: results only are printed on a single line < (where applicable). This is a way of getting a very compact report. < -r test number - selects specific rgb test. < -S seed. Any (uint) seed but (default) 0 surpresses per-test, < fully automated reseeding from /dev/random if available or the < clock if not (where the latter is NOT really desireable). < -s test number - selects specific sts test. < -t count - sets the number of random entities used in each test, where < possible. Be warned -- some tests will take a long time with the < default value of 10000. Read the test synopses for suggested settings < for -t or use -a first. < -u test number - selects specific user-developed test, if you've added < one or more to this tool. dieharder provides this interface to make < it easy to add your own tests. < -v verbose flag -- controls the verbosity of the output for debugging < only. Probably of little use to non-developers, and developers can < read the enum(s) in dieharder.h and the test sources to see which < flag values turn on output on which routines. 1 is "all" and will < result in a fairly detailed trace of program activity. < -x,-y,-z number - Some tests have parameters that can safely be varied < from their default value. For example, in the diehard birthdays test, < one can vary the number of "dates" drawn from the "year" of some < length, which can also be varied. -x 2048 -y 30 alters these two < values but should still run fine. < < NOTE WELL: The "bogomegarates" returned by this tool are BOGUS < and may not be even approximately correct in your context. Also, the < quality assessment(s) for the rngs may, in fact, be completely incorrect < or misleading. Use them at your Own Risk! Be Warned! <
checking for unstated dependencies in vignettes ... OK
checking package vignettes in ‘inst/doc’ ... OK
checking running R code from vignettes ... [2s/2s] OK ‘RDieHarder.Rnw’... [2s/2s] OK
checking re-building of vignette outputs ... [10s/11s] OK
checking PDF version of manual ... [4s/5s] OK
DONE Status: OK
using check arguments '--no-clean-on-error '