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

Add downgrade workflow, fix lower bounds #2078

Merged
merged 6 commits into from
Nov 12, 2024
Merged

Add downgrade workflow, fix lower bounds #2078

merged 6 commits into from
Nov 12, 2024

Conversation

Sbozzolo
Copy link
Member

@Sbozzolo Sbozzolo commented Nov 11, 2024

This commit adds the downgrade github action and cleans up some incorrect lower bounds. I also removed a couple of packages that could be trivially removed.

Closes #1781

@Sbozzolo Sbozzolo force-pushed the gb/downgrade branch 13 times, most recently from 3f2adb2 to ac944fb Compare November 11, 2024 03:23
@charleskawczynski
Copy link
Member

I think we can split this PR up into:

  • Qualifying packages (using ... --> import ...)
  • Removing unused packages (Combinatorics)
  • Downgrade GHA

I'm happy to help peel off some pieces

@Sbozzolo
Copy link
Member Author

Removing some of the packages was needed to add the downgrade job, otherwise it was impossible to solve the version constraint (see some of the failed github actions).

Also, the job is still failing, so I haven't fully figured out what needs to be done.

I'd like to merge this (fixing the lower bounds) before making the new release, if possible. The lower bounds of the compats are wrong, which makes adding downgrade to other packges harder.

@charleskawczynski
Copy link
Member

I'd like to merge this (fixing the lower bounds) before making the new release, if possible. The lower bounds of the compats are wrong, which makes adding downgrade to other packges harder.

I would like to merge this too, but I think I'd prefer we don't wait for the next release. I was hoping to make a release today. We can always make another quick patch release soon after. I'd like to have frequent release cycles when we have frequent delivered features/improvements, and there are a bunch in main right now.

@Sbozzolo
Copy link
Member Author

I'd like to merge this (fixing the lower bounds) before making the new release, if possible. The lower bounds of the compats are wrong, which makes adding downgrade to other packges harder.

I think I can fix this in the next hour or so.

@Sbozzolo Sbozzolo force-pushed the gb/downgrade branch 4 times, most recently from 8ab7a38 to e507b1d Compare November 11, 2024 18:11
@Sbozzolo
Copy link
Member Author

The downgrade tests passed. I am rebasing and this should be ready.

NEWS.md Outdated Show resolved Hide resolved
@charleskawczynski
Copy link
Member

Ah, sorry, I didn't realize that #2080 would result in conflicts. I hope it's not too complicated to fix. I support merging this once it's resolved / rebased.

The only data structure needed in OrderedDict, which is also provided by
DataStructures (which is already a dependency of ClimaCore)
It is only used in one place, where it can be easily inlined
This commit adds the downgrade github action and cleans up some incorrect lower
bounds.
This test was failing with
```
/home/runner/work/ClimaCore.jl/ClimaCore.jl/test/Spaces/unit_spaces.jl:58
  Expression: coord_slab[slab_index(4)] == Geometry.XPoint{FT}(5)
   Evaluated: XPoint(4.999999999999999) == XPoint(5.0)
```
@Sbozzolo Sbozzolo merged commit 40ce7f7 into main Nov 12, 2024
33 of 34 checks passed
@Sbozzolo Sbozzolo deleted the gb/downgrade branch November 12, 2024 02:06
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