You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Neal Richardson (Jira)" <ji...@apache.org> on 2020/10/10 18:34:00 UTC
[jira] [Created] (ARROW-10270) [R] Fix CSV timestamp_parsers test
on R-devel
Neal Richardson created ARROW-10270:
---------------------------------------
Summary: [R] Fix CSV timestamp_parsers test on R-devel
Key: ARROW-10270
URL: https://issues.apache.org/jira/browse/ARROW-10270
Project: Apache Arrow
Issue Type: Bug
Components: R
Reporter: Neal Richardson
Assignee: Neal Richardson
Fix For: 2.0.0
Apparently there is a change in the development version of R with respect to timezone handling. I suspect it is this: https://github.com/wch/r-source/blob/trunk/doc/NEWS.Rd#L296-L300
It causes this failure:
{code}
── 1. Failure: read_csv_arrow() can read timestamps (@test-csv.R#216) ─────────
`tbl` not equal to `df`.
Component "time": 'tzone' attributes are inconsistent ('UTC' and '')
── 2. Failure: read_csv_arrow() can read timestamps (@test-csv.R#219) ─────────
`tbl` not equal to `df`.
Component "time": 'tzone' attributes are inconsistent ('UTC' and '')
{code}
This needs to be fixed for the CRAN release because they check on the devel version. But it doesn't need to block the 2.0 release candidate because I can (at minimum) skip these tests before submitting to CRAN (FYI [~kszucs])
I'll also add a CI job to test on R-devel. I just removed 2 R jobs so we can afford to add one back.
cc [~romainfrancois]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)