-
-
Notifications
You must be signed in to change notification settings - Fork 784
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
Measure flakyness on Windows CI #4742
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.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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. |
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?