CRAN Package Check Results for Package hyd1d

Last updated on 2024-05-29 08:56:22 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.5.1 15.82 134.24 150.06 OK
r-devel-linux-x86_64-debian-gcc 0.5.1 13.19 150.10 163.29 OK
r-devel-linux-x86_64-fedora-clang 0.5.1 258.48 OK
r-devel-linux-x86_64-fedora-gcc 0.5.1 267.82 OK
r-devel-windows-x86_64 0.5.1 14.00 154.00 168.00 OK
r-patched-linux-x86_64 0.5.1 13.68 132.23 145.91 OK
r-release-linux-x86_64 0.5.1 14.93 132.45 147.38 OK
r-release-macos-arm64 0.5.1 211.00 OK
r-release-windows-x86_64 0.5.1 15.00 158.00 173.00 OK
r-oldrel-macos-arm64 0.5.1 230.00 OK
r-oldrel-macos-x86_64 0.5.1 320.00 OK
r-oldrel-windows-x86_64 0.5.1 20.00 698.00 718.00 WARN

Check Details

Version: 0.5.1
Check: startup messages can be suppressed
Result: NOTE curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21044 ms: Couldn't connect to server It was not possible to update the gauging data. Try again later! It looks like this package (or a package it requires) has a startup message which cannot be suppressed: see ?packageStartupMessage. Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: dependencies in R code
Result: NOTE curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21017 ms: Couldn't connect to server Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: S3 generic/method consistency
Result: WARN curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21029 ms: Couldn't connect to server See section 'Generic functions and methods' in the 'Writing R Extensions' manual. Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: replacement functions
Result: WARN curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21024 ms: Couldn't connect to server The argument of a replacement function which corresponds to the right hand side must be named 'value'. Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: foreign function calls
Result: NOTE curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21026 ms: Couldn't connect to server See chapter 'System and foreign language interfaces' in the 'Writing R Extensions' manual. Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: R code for possible problems
Result: NOTE curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21067 ms: Couldn't connect to server Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: Rd files
Result: WARN curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21022 ms: Couldn't connect to server Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: for missing documentation entries
Result: WARN curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21041 ms: Couldn't connect to server 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-oldrel-windows-x86_64

Version: 0.5.1
Check: for code/documentation mismatches
Result: WARN curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21011 ms: Couldn't connect to server curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21025 ms: Couldn't connect to server curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21029 ms: Couldn't connect to server Flavor: r-oldrel-windows-x86_64

Version: 0.5.1
Check: Rd \usage sections
Result: NOTE curl: (28) Failed to connect to hyd1d.bafg.de port 443 after 21070 ms: Couldn't connect to server 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. Flavor: r-oldrel-windows-x86_64