Bump dotnet-stryker to 5.0.0 and give the full mutation run five hours - #120
Merged
Merged
Conversation
The full run of Pulse, 715 mutants, took 2 h 15 min at the 0.2.0 release against a limit of 150 minutes, and 3 h 18 min and 3 h 33 min in two runs on 2026-10-02: at 150 the run is cancelled and reports no score. 300 minutes leaves room for a slow runner. The pull request run keeps its 20 minutes.
Two full runs on the same commit and the same day, one per version, give the same scores: Pulse 94.48 % on both (4.16.0: 685 killed, 30 survived; 5.0.0: 681 killed, 4 timed out, 30 survived) and Pulse.Otlp 81.00 % on both (179 killed, 29 survived). Four mutants that 4.16.0 killed are caught by a timeout on 5.0.0, which counts the same. Pulse took 3 h 18 min on 5.0.0 against 3 h 33 min on 4.16.0, and Pulse.Otlp 7 min against 14. 5.0.0 targets the .NET 10 runtime, which this lane already installs. Its other breaking change, the baseline provider following the output path, does not apply: the lane uses no baseline.
This was referenced Oct 2, 2026
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.
Takes Dependabot's bump of dotnet-stryker to 5.0.0 (#115) with the one thing it needs to be judged, a full run, and the one thing that run showed: the lane's time limit is too short on either version.
Same scores on both versions
Two full runs on the same commit and the same day, one per version:
Both versions create the same 1,454 and 514 mutants and test the same 715 and 208. Four mutants that 4.16.0 killed are caught by a timeout on 5.0.0, which counts the same; the survivors are as many. The thresholds (83 and 70) are far below both.
Of the two breaking changes of 5.0.0, one is already met (it targets the .NET 10 runtime, which the lane installs) and the other does not apply (the baseline provider, which the lane does not use).
The full run gets five hours
The first full run on 5.0.0 was cancelled at the lane's limit of 150 minutes and reported no score. It was not the new version: the 4.16.0 run of the same day needed 3 h 33 min. At the 0.2.0 release the run took 2 h 15 min, fifteen minutes under the limit. The limit of the full run goes from 150 to 300 minutes; the pull request run keeps its 20.
The weekly run reads this file from
main, where the limit is still 150: that needs the same change there.Closes #115.