Measure flakyness on Windows CI#4742
Merged
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4742 +/- ##
============================================
- Coverage 84.74% 84.69% -0.05%
+ Complexity 3431 3418 -13
============================================
Files 491 490 -1
Lines 11270 11235 -35
Branches 2074 2068 -6
============================================
- Hits 9551 9516 -35
- Misses 673 675 +2
+ Partials 1046 1044 -2
Continue to review full report at Codecov.
|
runningcode
approved these changes
Apr 21, 2022
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
picklebento
approved these changes
Jun 19, 2022
Member
|
Let's monitor Gradle enterprise / Test when this is merged. If this pipeline works, GE is an actual savior for monitoring and tackling test flakiness without manual CI scripting. |
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
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.
We all know that our Windows & JDK11 CI is flaky. It show flakyness. Here I have a list of 8 failed builds because of that:
We had this problem already with Windows & JDK8 and we "fixed" it by disabling that combination: #4403
Right now we don't have flakyness information on of Gradle enterprise instance https://ge.detekt.dev/scans/tests because we need to activate this plugin: https://docs.gradle.com/enterprise/flaky-test-detection/
That's what this PR does, add that plugin. I don't like the idea of "retry" tests but I think that this is the only option that we have right now.
Open question: Should I enable it only for Windows?