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

include gufe main and latest in ci matrix #1036

Merged
merged 13 commits into from
Dec 6, 2024
Merged

include gufe main and latest in ci matrix #1036

merged 13 commits into from
Dec 6, 2024

Conversation

atravitz
Copy link
Contributor

@atravitz atravitz commented Dec 5, 2024

CI is currently failing because of changes on gufe main. We should (at least for now) run CI for both gufe main and latest, since we expect it to pass on latest but fail on main.

@atravitz atravitz requested a review from mikemhenry December 5, 2024 17:54
Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

codecov bot commented Dec 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.83%. Comparing base (be3433c) to head (cb25ce5).
Report is 15 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1036      +/-   ##
==========================================
- Coverage   94.59%   92.83%   -1.77%     
==========================================
  Files         134      134              
  Lines        9940     9961      +21     
==========================================
- Hits         9403     9247     -156     
- Misses        537      714     +177     
Flag Coverage Δ
fast-tests 92.83% <ø> (?)
slow-tests ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link
Member

@IAlibay IAlibay left a comment

Choose a reason for hiding this comment

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

Couple of things:

  1. If you do this, then you have to ammend the env yaml file
  2. This will use up all our runners when we do a merge with slow tests - i.e. it's too many runners.

@IAlibay
Copy link
Member

IAlibay commented Dec 5, 2024

See https://github.com/OpenFreeEnergy/openfe/actions/runs/12186104840/job/33993854139?pr=1036#step:9:617

Even though it's set at latest, the issue you're facing is that you've already pip installed gufe, so mamba attempts to installs, finds that you already have a working version and does nothing.

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

1 similar comment
Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

1 similar comment
Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

Copy link
Member

@IAlibay IAlibay left a comment

Choose a reason for hiding this comment

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

The main question I have is "how long are we planning to do this".

One key issue I could see is that openfe adapts to match a behaviour from gufe (see for example when we dropped the key stability tests) and then "latest" fails, but that's intentional because we've fixed things to match with upstream.

.github/workflows/ci.yaml Outdated Show resolved Hide resolved
.github/workflows/ci.yaml Outdated Show resolved Hide resolved
Copy link

github-actions bot commented Dec 5, 2024

🚨 API breaking changes detected! 🚨

@atravitz
Copy link
Contributor Author

atravitz commented Dec 5, 2024

@mikemhenry I see there's api-breaking changes flagged here - where can I get more details on this?

edit: I found the details (here)

@atravitz atravitz self-assigned this Dec 5, 2024
@atravitz atravitz marked this pull request as ready for review December 5, 2024 23:05
Copy link

github-actions bot commented Dec 6, 2024

🚨 API breaking changes detected! 🚨

1 similar comment
Copy link

github-actions bot commented Dec 6, 2024

🚨 API breaking changes detected! 🚨

Copy link
Member

@IAlibay IAlibay left a comment

Choose a reason for hiding this comment

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

this looks good thanks!

Copy link

github-actions bot commented Dec 6, 2024

🚨 API breaking changes detected! 🚨

@atravitz atravitz requested a review from IAlibay December 6, 2024 22:57
@atravitz atravitz merged commit e12e07c into main Dec 6, 2024
12 of 13 checks passed
@atravitz atravitz deleted the add_latest_to_ci branch December 6, 2024 23:36
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