-
Notifications
You must be signed in to change notification settings - Fork 683
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
JUnit XML dumping fails #1383
Comments
Are you running kitchen-inspec with multiple suites in parallel? |
Yeah, I had concurrency set to 3. After filing the bug, I set it to 1 after realizing that might be it. Since then the problem hasn't popped up. |
This issue is related to inspec/kitchen-inspec#119. I expect it to be a general problem in kitchen inspec and not related to our junit reporter. If it is okay for you, lets track this in inspec/kitchen-inspec#119 |
Sure, let's do that. |
Description
I'm a bit unsure where to file this bug. I use test-kitchen to run InSpec tests on our Chef cookbooks using Bamboo. The verifier's output is set to JUnit. Every now and then the tests fail.
I modified the output a bit to get just the relevant stuff. The "failed to parse test result" lines are from Bamboo's JUnit parser.
The reason it fails is that, suite1's XML is empty and suite2's XML will have suite1's test results twice.
Possibly related to this sj26/rspec_junit_formatter#45
Might be a bit hard to replicate, as this doesn't happen on every run. Could be a concurrency issue of some sort, as the timestamps on the two XML files are the same.
InSpec and Platform Version
Running on CentOS 7 with:
inspec (1.7.2)
kitchen-inspec (0.17.0)
rspec_junit_formatter (0.2.3)
test-kitchen (1.14.2)
rspec (3.5.0)
rspec-core (3.5.4)
The text was updated successfully, but these errors were encountered: