Issue #3316: use pitest testing of checks.sizes package in shippable CI #3631
Conversation
This file contains 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
Current coverage is 100% (diff: 100%)@@ master #3631 diff @@
=====================================
Files 275 275
Lines 13325 13325
Methods 0 0
Messages 0 0
Branches 3037 3037
=====================================
Hits 13325 13325
Misses 0 0
Partials 0 0
|
|
pitest validation on "size" package took - 5m 55s |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #3316.
Due to the fact that pitest works for a long time, and CI will perceive it as an timeout error, we need to split pitest testing packages on maven profiles. At first I added the sizes package of checks to separate maven profile and added pitest testing of this package in shippable CI.