Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] test_parquet_write_roundtrip_datetime_with_legacy_rebase fails with "year 0 is out of range" #9820

Closed
jlowe opened this issue Nov 21, 2023 · 0 comments · Fixed by #9821
Assignees
Labels
bug Something isn't working test Only impacts tests

Comments

@jlowe
Copy link
Member

jlowe commented Nov 21, 2023

In premerge build, saw test_parquet_write_roundtrip_datetime_with_legacy_rebase fail like this:

test_parquet_write_roundtrip_datetime_with_legacy_rebase[ts_rebase_read0-ts_rebase_write1-TIMESTAMP_MICROS-Array(Struct(['child0', Date],['child1', Timestamp]))][DATAGEN_SEED=1700582301, INJECT_OOM] 
[...]
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = TimestampType(), ts = -62135587472896789

    def fromInternal(self, ts: int) -> datetime.datetime:
        if ts is not None:
            # using int to avoid precision loss in float
>           return datetime.datetime.fromtimestamp(ts // 1000000).replace(microsecond=ts % 1000000)
E           ValueError: year 0 is out of range
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working test Only impacts tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants