-
Notifications
You must be signed in to change notification settings - Fork 204
CI: Rework workflow to avoid testing #6897
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6897 +/- ##
==========================================
+ Coverage 80.06% 80.88% +0.82%
==========================================
Files 246 246
Lines 77866 78101 +235
==========================================
+ Hits 62340 63173 +833
+ Misses 15526 14928 -598 🚀 New features to boost your workflow:
|
|
Seems like our runner is impacted by nodejs/node#56645 so we cannot use astral-sh/setup-uv@v7. Changing to the latest v6 available. |
Samuelopez-ansys
left a comment
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.
powerful!
I just released https://github.com/astral-sh/setup-uv/releases/tag/v7.1.4 which should fix this issue. |
Description
This PR is aiming at handling the first bullet point of #6896
Here we mitigate resource contention by avoiding to run the test for extensions / emit / solver solutions, unless there is a modification in the folder associated to each topic.
The tests are still run nightly and we'll have to consult them to know if something is going wrong with them.
Tests are still running when the PR is merge to ensure that we have code coverage fully evaluated on the repo. We could investigate if running the test nightly can be leveraged to still get a code coverage for the repo without running the test on main but that should be done in a second PR.
Pinging @jsalant22 @myoung301 @ramin4667 for visibility.
Issue linked
Associated to #6896
Checklist