Skip to content

[SUREFIRE-1737] Fix disable in statelessTestsetReporter #816

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

Merged
merged 1 commit into from
Mar 24, 2025

Conversation

slawekjaranowski
Copy link
Member

  • old property disableXmlReport should be null by default
  • add ITs
  • small cleanups

https://issues.apache.org/jira/browse/SUREFIRE-1737

- old property `disableXmlReport` should be null by default
- add ITs
- small cleanups
@slawekjaranowski slawekjaranowski self-assigned this Mar 23, 2025
@slawekjaranowski slawekjaranowski added the bug Something isn't working label Mar 23, 2025
@slawekjaranowski slawekjaranowski requested a review from olamy March 23, 2025 12:03
@slawekjaranowski slawekjaranowski merged commit b7381a4 into apache:master Mar 24, 2025
26 checks passed
@slawekjaranowski slawekjaranowski deleted the UREFIRE-1737-fix-2 branch March 24, 2025 08:10
@github-actions github-actions bot added this to the next-release milestone Mar 24, 2025
@fslevoaca-ionos
Copy link

fslevoaca-ionos commented Mar 31, 2025

Failed tests are no longer displayed inside target/surefire-reports/report.txt/xml
Possible the fix for current issue would have introduced this critical regression bug inside maven-surefire 3.5.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants