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.

Sign up for GitHub

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

Jump to bottom

Mark test_use_cftime_false_standard_calendar_in_range as an expected failure #8996

Merged
merged 1 commit into from
May 3, 2024
Merged

Mark test_use_cftime_false_standard_calendar_in_range as an expected failure #8996

merged 1 commit into from
May 3, 2024

Conversation

spencerkclark
Copy link
Member

Per #8844 (comment), for the time being this marks test_use_cftime_false_standard_calendar_in_range as an expected failure under NumPy 2. Hopefully we'll be able to fix the upstream issue in pandas eventually.

@spencerkclark spencerkclark added the run-upstream Run upstream CI label May 3, 2024
@spencerkclark spencerkclark mentioned this pull request May 3, 2024
Closed
@dcherian dcherian merged commit c2cd1dd into pydata:main May 3, 2024
29 of 31 checks passed
andersy005 added a commit that referenced this pull request May 3, 2024
@andersy005
Merge remote-tracking branch 'origin/main' into backend-indexing
2fd3b8b 
* origin/main:
  call `np.cross` with 3D vectors only (#8993)
  Mark `test_use_cftime_false_standard_calendar_in_range` as an expected failure (#8996)
  Migration of datatree/ops.py -> datatree_ops.py (#8976)
  avoid a couple of warnings in `polyfit` (#8939)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
run-upstream Run upstream CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@spencerkclark @dcherian