> tibor17The fact that Jenkins plugins are parsing this XML without any problem means that they do not mind in the elements of (rerunError, rerunFailure, flakyFailure, flakyError)
Not true at all, plugins like xunit use the XSD to validate the XML (and with 2.22.1 is broken, files are skipped). It's not clear for me what is the gain of the stacktrace element and make rerun elements different from failure and error.
EDIT: you missed to list the component that supports flaky elements... xunit and flaky-test-handler and for this reason you did get a response in time because no one of major interested people was informed. I'm here now because the new version had broken our organisation pipelines and I got this link from SUREFIRE-1559.
tibor17 Does SUREFIRE-1559 imply a breaking change in Maven Surefire?
> This should be fixed in Maven Surefire. If you use this XML and visualize the reports, pls adapt to the fix.
What is ETA of the fix? IIUC there is only an issue report without confirmed ETA or action plan (e.g. major version number bump, etc.).
Whatever the fix is needed on the Jenkins side, we will need to support both previous and new formats