You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[R] R builds failing with error 'Invalid: Timestamps already have a timezone: 'UTC'. Cannot localize to 'UTC'' #35633
I see that this is #35612. Now, that was actually passing on main, so it might also have been triggered by #35449 (which is failing with this on main, and was actually also already failing on the PR ..)
My assumption is that the fix of #35449 caused one of the test dates to become UTC, causing the failure. If that's the case, we will need to fix the test I think
This adds the format "%T%z", and that will now actually result in a tz-aware timestamp, while before it didn't parse the timezone correctly (that's the fix in #35449).
And "strptime" dplyr binding ends up calling assume_timezone, which will not work if the timestamp already has a timezone.
changed the title [-][C++] R builds failing with error 'Invalid: Timestamps already have a timezone: 'UTC'. Cannot localize to 'UTC''[/-][+][R] R builds failing with error 'Invalid: Timestamps already have a timezone: 'UTC'. Cannot localize to 'UTC''[/+]on May 17, 2023
Activity
thisisnic commentedon May 17, 2023
This fails on the nightly builds, but I can't replicate this when locally, or when running it on PRs (see #3561).
jorisvandenbossche commentedon May 17, 2023
Was that done in a specific PR? (to understand what changed)
jorisvandenbossche commentedon May 17, 2023
I see that this is #35612. Now, that was actually passing on main, so it might also have been triggered by #35449 (which is failing with this on main, and was actually also already failing on the PR ..)
thisisnic commentedon May 17, 2023
Yep, it was in #35612
jorisvandenbossche commentedon May 17, 2023
My assumption is that the fix of #35449 caused one of the test dates to become UTC, causing the failure. If that's the case, we will need to fix the test I think
thisisnic commentedon May 17, 2023
You're right; it is failing on the CI on that PR, e.g. https://github.com/apache/arrow/actions/runs/4900485911/jobs/8751167526
jorisvandenbossche commentedon May 17, 2023
Here:
arrow/r/tests/testthat/test-dplyr-funcs-datetime.R
Line 292 in 99ef3aa
This adds the format
"%T%z", and that will now actually result in a tz-aware timestamp, while before it didn't parse the timezone correctly (that's the fix in #35449).And "strptime" dplyr binding ends up calling
assume_timezone, which will not work if the timestamp already has a timezone.[-][C++] R builds failing with error 'Invalid: Timestamps already have a timezone: 'UTC'. Cannot localize to 'UTC''[/-][+][R] R builds failing with error 'Invalid: Timestamps already have a timezone: 'UTC'. Cannot localize to 'UTC''[/+]GH-35633: [R] R builds failing with error 'Invalid: Timestamps alread…