tests.unit.test_date: test_date_parsing_errors[9999-12-31-Out of bounds] failed

[flaky-bot]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.

---

commit: af67adc
buildURL: Build Status, Sponge
status: failed

Test output

value = '9999-12-31', error = 'Out of bounds'
@pytest.mark.parametrize(
    "value, error",
    [
        ("thursday", "Bad date string: 'thursday'"),
        ("1-2-thursday", "Bad date string: '1-2-thursday'"),
        ("1-2-3-4", "Bad date string: '1-2-3-4'"),
        ("1-2-3.f", "Bad date string: '1-2-3.f'"),
        ("1-d-3", "Bad date string: '1-d-3'"),
        ("1-3", "Bad date string: '1-3'"),
        ("1", "Bad date string: '1'"),
        ("", "Bad date string: ''"),
        ("2021-2-99", "day is out of range for month"),
        ("2021-99-1", "month must be in 1[.][.]12"),
        ("10000-1-1", "year 10000 is out of range"),
        # Outside of min/max values pandas.Timestamp.
        ("0001-01-01", "Out of bounds"),
        ("9999-12-31", "Out of bounds"),
        ("1677-09-21", "Out of bounds"),
        ("2262-04-12", "Out of bounds"),
    ],
)
def test_date_parsing_errors(value, error):


  with pytest.raises(ValueError, match=error):


E       Failed: DID NOT RAISE <class 'ValueError'>
tests/unit/test_date.py:154: Failed

[flaky-bot]

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (af67adc), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[tswast]

Pandas now supports microsecond-precision pandas-dev/pandas#49034

We'll need to add our own validation for nanosecond-precision supported dates as a stop-gap.