-
Notifications
You must be signed in to change notification settings - Fork 333
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
On latest SBT (1.2.6) JUnit reporter can mangle output files #1427
Comments
testForkedParallel
I believe the cause is a regression in SBT. sbt/sbt#4400 Let me close this issue for now as there's nothing to be fixed in scalatest |
For the record, disabling either SBT's built-in |
Thanks to your comment, saved my time. I suggest writing the report using atomic write. Users should notice the redundancy in the reports anyway... |
Arguably, an "experimental" plugin shouldn't be enabled by default. This could be considered a mistake from sbt. |
This can cause issues with Junit XML output getting mangled causing unstable builds in Jenkins. See scalatest/scalatest#1427
Disable JUnitXmlReportPlugin in the project configuration to prevent issues related to scalatest/scalatest#1427. This change ensures smoother build and testing processes.
Jenkins reporter then fails with:
Examination of this file shows that some contents is written twice, as if two reporters tried to write to the same file without locking.
We've been using forked parallel testing for a while but only after upgrading to SBT 1.2.6 did the problem surface.
EDIT: The bug still shows after disabling forked parallel testing
EDIT2: The bug still shows after disabling forking.
The text was updated successfully, but these errors were encountered: