tests.unit.test_dtypes: many tests failed

[flaky-bot]

Many tests failed at the same time in this package.

• I will close this issue when there are no more failures in this package and
  there is at least one pass.
• No new issues will be filed for this package until this issue is closed.
• If there are already issues for individual test cases, I will close them when
  the corresponding test passes. You can close them earlier, if you prefer, and
  I won't reopen them while this issue is still open.

Here are the tests that failed:

• test_array_construction[None-dbtime]
• test_array_construction[_from_sequence-dbtime]
• test_array_construction[_from_sequence_of_strings-dbtime]
• test_timearray_slicing[dbtime]
• test_item_assignment[dbtime]
• test_array_assignment[dbtime]
• test_astimedelta[<m8]
• test_astimedelta[<m8[s]]
• test_astimedelta[<m8[ms]]
• test_astimedelta[<m8[us]]
• test_astimedelta[<m8[ns]]
• test_astimedelta[timedelta]
• test_astimedelta[timedelta64]
• test_astimedelta[timedelta64[s]]
• test_astimedelta[timedelta64[ms]]
• test_astimedelta[timedelta64[us]]
• test_astimedelta[timedelta64[ns]]
• test_min_max_median[dbtime]

---

commit: 508564f
buildURL: Build Status, Sponge
status: 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 (508564f), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[chalmerlowe]

Based on conversation in the pandas github issue tracker, the root cause of these failing tests appears to be that the pandas system is trying to store too large a number in an int32 memory location. The bug has been added to the pandas 1.5 milestone (pandas is currently at 1.5.0 release candidate stage)

See:
pandas-dev/pandas#48255