CRAN Package Check Results for Package opencpu

Last updated on 2024-11-22 03:52:44 CET.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	2.2.14	4.44	35.31	39.75	WARN
r-devel-linux-x86_64-debian-gcc	2.2.14	3.11	27.29	30.40	OK
r-devel-linux-x86_64-fedora-clang	2.2.14			69.59	OK
r-devel-linux-x86_64-fedora-gcc	2.2.14			74.58	OK
r-devel-windows-x86_64	2.2.14	7.00	56.00	63.00	OK
r-patched-linux-x86_64	2.2.14	3.96	34.10	38.06	OK
r-release-linux-x86_64	2.2.14	4.29	34.15	38.44	OK
r-release-macos-arm64	2.2.14			29.00	OK
r-release-macos-x86_64	2.2.14			55.00	OK
r-release-windows-x86_64	2.2.14	7.00	55.00	62.00	NOTE
r-oldrel-macos-arm64	2.2.14			34.00	OK
r-oldrel-macos-x86_64	2.2.14			48.00	OK
r-oldrel-windows-x86_64	2.2.14	7.00	56.00	63.00	NOTE

Check Details

Version: 2.2.14
Check: whether startup messages can be suppressed
Result: NOTE Authorization required, but no authorization protocol specified It looks like this package (or a package it requires) has a startup message which cannot be suppressed: see ?packageStartupMessage. Flavor: r-devel-linux-x86_64-debian-clang

Version: 2.2.14
Check: for missing documentation entries
Result: WARN Authorization required, but no authorization protocol specified All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-clang

Version: 2.2.14
Check: for code/documentation mismatches
Result: WARN Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified Flavor: r-devel-linux-x86_64-debian-clang

Version: 2.2.14
Check: package dependencies
Result: NOTE Package suggested but not available for checking: 'unix' Flavors: r-release-windows-x86_64, r-oldrel-windows-x86_64