Junit result xml file output is corrupted
See original GitHub issueDescribe the bug
- JUnit output is not valid.
- It has an extra line at the top of the xml file:
'NoneType' object is not iterable
To Reproduce Steps to reproduce the behavior:
- Jenkins pipeline ran the command for checkov to scan which was
checkov -d terraform --no-guide -o junitxml
2.Jenkins error message on the buildresults.xml.[failed-to-read]
- Saw that there is an extra line in the Junit xml file
'NoneType' object is not iterable
Expected behavior JUnit xml result should a valid xml file
Desktop (please complete the following information):
- OS: Ubuntu 20.04
- Checkov Version2.0.604
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Unable to get hudson to parse JUnit test output XML
The problem is, whenever I tell ant to publish the JUnit test results, and then point it to either the raw test result...
Read more >Jenkins fails to read Junit xml for publishing Junit Test Results
I am using Jenkins for CI, and as such, I am creating a junit xml file after my test suites executes to post...
Read more >JUnit feature should be able to parse JUnit.xml files with large ...
Problem. As a developer (Sasha) when a JUnit XML file is created by my pipeline that contains very large system-output nodes (8MB +), ......
Read more >JUnit Parser task in Bamboo shows 'Failed to parse test result ...
As the error states, Bamboo is unable to parse the test file. This may be caused by: Incorrect XML format; Invalid characters in...
Read more >XML report encoding - Google Groups
I use a Ant task to run tests and convert to junit report. Conversion ... corrupted." ... Which files are you referring to,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kaiyuanlim great thanks for confirming 👍
Update: Please close this issue. Seems like it has been fixed