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

ci: test NumPy < 1.17 #2142

Merged
merged 3 commits into from
Jan 19, 2023
Merged

ci: test NumPy < 1.17 #2142

merged 3 commits into from
Jan 19, 2023

Conversation

agoose77
Copy link
Collaborator

@agoose77 agoose77 commented Jan 19, 2023

My recollection of this test special case is that we want to ensure our oldest NumPy supported version is building & testing properly. I've set this to 1.14.5 for now, which is what oldest-supported-numpy reports for 3.7. This CI configuration was seemingly backwards.

@codecov
Copy link

codecov bot commented Jan 19, 2023

Codecov Report

Merging #2142 (617d659) into main (b6e4c71) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files
Impacted Files Coverage Δ
src/awkward/_slicing.py 85.00% <0.00%> (+0.38%) ⬆️

@agoose77 agoose77 temporarily deployed to docs-preview January 19, 2023 21:30 — with GitHub Actions Inactive
@agoose77 agoose77 requested a review from jpivarski January 19, 2023 21:33
Copy link
Member

@jpivarski jpivarski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be merged in version 2.1.0. It would be nice to have an alarm clock or something remind us about that, but I don't think there's any such feature. I could put it in my GTasks for late January.

@agoose77 agoose77 temporarily deployed to docs-preview January 19, 2023 21:43 — with GitHub Actions Inactive
@agoose77
Copy link
Collaborator Author

@jpivarski I think this can be merged now, no? It tests our current lower bound, and we can raise it to 1.17 when we make our next minor release.

@jpivarski
Copy link
Member

Oh, I was reading it backward! Yes, we should be testing our current minimum bound. This PR can be merged now (and its inverse has to wait until 2.1.0).

@agoose77 agoose77 enabled auto-merge (squash) January 19, 2023 21:52
@agoose77 agoose77 disabled auto-merge January 19, 2023 21:53
@agoose77 agoose77 merged commit d2f9325 into main Jan 19, 2023
@agoose77 agoose77 deleted the agoose77/ci-test-numpy-lower-bound branch January 19, 2023 21:53
douglasdavis pushed a commit to douglasdavis/awkward that referenced this pull request Jan 19, 2023
* ci: test NumPy < 1.17

* chore: drop old file

* ci: use 1.14.5 explicitly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants