-
Notifications
You must be signed in to change notification settings - Fork 421
Drop incremental-mutants
CI job (0.1)
#3954
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
Drop incremental-mutants
CI job (0.1)
#3954
Conversation
Previously, the `incremental-mutants` CI job was failing on ~every PR that made actual logic changes, and nobody seemed to really make any effort to address the failures. The failing CI jobs therefore just resulted in additional which in turn could have us getting used to failing CI, introducing some risk of acutal failures slipping through. Of course, it also took up some (considerable?) time in the CI queue that might be better spent on other jobs if no contributors are actually benefitting from the CI job. Here we therefore drop `incremental-mutants` from our CI for the time being.
👋 I see @valentinewallace was un-assigned. |
Will undraft once we reach a conclusive decision on #3948. |
Also included a second commit fixing |
Discussed this at the dev sync, everybody seemed to be in favor or at least not against dropping it. So undrafting. |
5ffe039
to
3b59329
Compare
3b59329
to
ddd31ef
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 0.1 #3954 +/- ##
==========================================
+ Coverage 87.40% 87.42% +0.02%
==========================================
Files 149 149
Lines 100751 100751
Branches 100751 100751
==========================================
+ Hits 88064 88085 +21
+ Misses 10441 10425 -16
+ Partials 2246 2241 -5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
👋 The first review has been submitted! Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer. |
Previously, the
incremental-mutants
CI job was failing on ~every PR that made actual logic changes, and nobody seemed to really make any effort to address the failures. The failing CI jobs therefore just resulted in additional which in turn could have us getting used to failing CI, introducing some risk of acutal failures slipping through. Of course, it also took up some (considerable?) time in the CI queue that might be better spent on other jobs if no contributors are actually benefitting from the CI job.Here we therefore drop
incremental-mutants
from our CI for the time being.