html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/7716#issuecomment-1498160636,https://api.github.com/repos/pydata/xarray/issues/7716,1498160636,IC_kwDOAMm_X85ZTB38,10647082,2023-04-05T21:05:34Z,2023-04-05T21:05:34Z,CONTRIBUTOR,"> CI says these are the tests we'd need to fix:

Chiming in from the pandas side on those failures, I think they are all expected https://pandas.pydata.org/docs/whatsnew/v2.0.0.html namely

* Since pandas supports `s`, `ms` and `us` numpy datetime resolutions now, I'm guessing that's why  `test_to_datetimeindex_out_of_range` and `test_should_cftime_be_used_source_outside_range` are failing
* For `test_sel_float`, `pd.Index` intentionally does not support `np.float16` as dtype anymore (we never had an indexing engine for this dtype)
* For `test_maybe_coerce_to_str`, this might be expected too as `Index` dtypes can hold `np.int32` types now","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1654022522