Uh oh!
There was an error while loading. Please reload this page.
ARROW-17386: [R] strptime tests not robust across platforms - #13854
Conversation
nealrichardson
left a comment
There was a problem hiding this comment.
The other thing I'd like to see is assertions that the result of strptime is not all NA. My guess about the CRAN issue is that we're testing a token that isn't supported anywhere else (in both R and Arrow), and the difference on his machine is that it does parse successfully in R bust still not in Arrow.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
kou
commented
Aug 12, 2022
You may want to export |
That's a good point! However lubridate's strptime supports |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Neal Richardson <neal.p.richardson@gmail.com>
rok
commented
Sep 9, 2022
Thanks for the review @nealrichardson ! I've addressed your comments and I think this is ready for another review round. |
rok
commented
Sep 12, 2022
CI issues don't seem related. |
ursabot
commented
Sep 13, 2022
Benchmark runs are scheduled for baseline = 6c675c3 and contender = 4ae26d1. 4ae26d1 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
ursabot
commented
Sep 13, 2022
['Python', 'R'] benchmarks have high level of regressions. |
@jonkeane We only change the test here. Is the regression misattributed or are these tests used in tcph or |
…3854) This is to resolve [ARROW-17386](https://issues.apache.org/jira/browse/ARROW-17386). Lead-authored-by: Rok <rok@mihevc.org> Co-authored-by: Rok Mihevc <rok@mihevc.org> Signed-off-by: Rok <rok@mihevc.org>
This is to resolve ARROW-17386.