-
Notifications
You must be signed in to change notification settings - Fork 21
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
switch ci matrix to test against gufe main again #1050
Conversation
🚨 API breaking changes detected! 🚨 |
48aa1d6
to
01f5803
Compare
🚨 API breaking changes detected! 🚨 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1050 +/- ##
==========================================
- Coverage 94.50% 92.79% -1.71%
==========================================
Files 134 134
Lines 9986 9986
==========================================
- Hits 9437 9267 -170
- Misses 549 719 +170
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
on second thought, I'm not sure there's reason for us to keep the CI failing with a test against |
I think we should be testing everything on main again now! |
🚨 API breaking changes detected! 🚨 |
🚨 API breaking changes detected! 🚨 |
8ccd6e4
to
bb3b75e
Compare
🚨 API breaking changes detected! 🚨 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Not sure if we need to update the required CI tests after this or not?
It's my understanding that we want to keep CI red until #1033 is closed, but I'm switching us to have the majority of our matrix test against
main
so that we are more likely to catch any new bugs.