CRAN Package Check Results for Package lubridate

Last updated on 2024-11-14 06:50:03 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.9.3 13.27 100.66 113.93 OK
r-devel-linux-x86_64-debian-gcc 1.9.3 8.74 64.58 73.32 ERROR
r-devel-linux-x86_64-fedora-clang 1.9.3 180.96 OK
r-devel-linux-x86_64-fedora-gcc 1.9.3 181.61 OK
r-devel-windows-x86_64 1.9.3 20.00 165.00 185.00 OK
r-patched-linux-x86_64 1.9.3 14.45 93.82 108.27 OK
r-release-linux-x86_64 1.9.3 12.20 93.97 106.17 OK
r-release-macos-arm64 1.9.3 59.00 OK
r-release-macos-x86_64 1.9.3 102.00 OK
r-release-windows-x86_64 1.9.3 20.00 143.00 163.00 OK
r-oldrel-macos-arm64 1.9.3 57.00 OK
r-oldrel-macos-x86_64 1.9.3 166.00 OK
r-oldrel-windows-x86_64 1.9.3 22.00 156.00 178.00 OK

Check Details

Version: 1.9.3
Check: tests
Result: ERROR Running ‘testthat.R’ [24s/27s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > library(testthat) > library(lubridate) Attaching package: 'lubridate' The following objects are masked from 'package:base': date, intersect, setdiff, union > > test_check("lubridate") [ FAIL 5 | WARN 0 | SKIP 11 | PASS 3061 ] ══ Skipped tests (11) ══════════════════════════════════════════════════════════ • FIXME: activate when timechange#29 isfixed (1): 'test-periods.R:650:3' • FIXME: time_length should be same on sides of DST? (1): 'test-timespans.R:55:3' • FIXME: ymd_hms OSz parsing (2): 'test-parsers.R:263:3', 'test-parsers.R:278:3' • On CRAN (7): 'test-namespace.R:33:3', 'test-namespace.R:44:3', 'test-ops-integer-division.R:17:3', 'test-parsers.R:1122:3', 'test-parsers.R:1141:3', 'test-pretty.R:4:3', 'test-vctrs.R:549:3' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-format_ISO8601.R:39:3'): Formatting a datetime works ───────── format_ISO8601(...) (`actual`) not equal to "2018-02-01T03:04:05-0500" (`expected`). `actual`: "2018-02-01T03:04:05+0000" `expected`: "2018-02-01T03:04:05-0500" usetz is respected with datetimes ── Failure ('test-format_ISO8601.R:43:3'): Formatting a datetime works ───────── format_ISO8601(...) (`actual`) not equal to "2018-02-01T08:04:05Z" (`expected`). `actual`: "2018-02-01T03:04:05Z" `expected`: "2018-02-01T08:04:05Z" usetz='Z' is respected with datetimes ── Failure ('test-format_ISO8601.R:52:3'): Formatting a datetime works ───────── format_ISO8601(...) (`actual`) not equal to "2018-0500" (`expected`). `actual`: "2018+0000" `expected`: "2018-0500" precision is respected (y) with timezone ── Failure ('test-format_ISO8601.R:128:3'): Formatting an Interval works ─────── format_ISO8601(...) (`actual`) not equal to "2018-02-01T00:00:00-0500/2018-03-04T00:00:00-0500" (`expected`). `actual`: "2018-02-01T05:00:00+0000/2018-03-04T05:00:00+0000" `expected`: "2018-02-01T00:00:00-0500/2018-03-04T00:00:00-0500" interval formatting respects timezone ── Failure ('test-parsers.R:519:3'): AM/PM indicators are parsed correctly ───── parse_date_time2("12/17/1996 04:00:00 PM", "mdYHMSp", tz = "CET") (`actual`) not equal to ymd_hms("1996-12-17 16:00:00", tz = "CET") (`expected`). `actual`: "1996-12-17 16:00:00" `expected`: "1996-12-17 15:00:00" [ FAIL 5 | WARN 0 | SKIP 11 | PASS 3061 ] Error: Test failures Execution halted Flavor: r-devel-linux-x86_64-debian-gcc