ci: Stop running mutation tests using stryker#496
Merged
Conversation
since they were running for 5+ hours and because of that only on master. Since we have quite a good code coverage now (>80% total), I would argue it's not worth all the compute invested on each master commit. I will instead work on reporting coverage in PRs and add a badge for the master branch
|
New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: @stryker-mutator/[email protected] |
Member
Author
|
@brodybits since you introduced this, I will keep this open until next Sunday to give you a chance to veto the change with some arguments (or a PR that speeds up the run substantially?). |
This was referenced Sep 26, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
since they were running for 5+ hours and because of that only on master, which is also why it is sometimes canceled. And I have not looked into the results for a long time.
Since we have quite a good code coverage now (>80% total), I would argue it's not worth all the compute invested on each master commit.
I will instead work on reporting coverage in PRs and add a badge for the master branch