dajac opened a new pull request, #14862:
URL: https://github.com/apache/kafka/pull/14862

   Includes https://github.com/apache/kafka/pull/14687 and 
https://github.com/apache/kafka/pull/14850.
   
   This patch adds the `reports.junitXml.mergeReruns` setting to gradle build. 
From the 
[doc](https://docs.gradle.org/current/userguide/java_testing.html#mergereruns):
   
   > When mergeReruns is enabled, if a test fails but is then retried and 
succeeds, its failures will be recorded as <flakyFailure> instead of <failure>, 
within one <testcase>. This is effectively the reporting produced by the 
[surefire plugin of Apache 
Maven™](https://maven.apache.org/components/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html)
 when enabling reruns. If your CI server understands this format, it will 
indicate that the test was flaky. If it does not, it will indicate that the 
test succeeded as it will ignore the <flakyFailure> information. If the test 
does not succeed (i.e. it fails for every retry), it will be indicated as 
having failed whether your tool understands this format or not.
   
   The patch also increases the `maxTestRetryFailures` to `50`.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to