Skip to content

Commit

Permalink
CI - Potential fix for Circle to parse errors
Browse files Browse the repository at this point in the history
I suspect that circleci wants an <error> tag instead of a <failure> one
to properly register a test as failing in the UI. We shall see.

(cherry picked from commit f7ee43f)
  • Loading branch information
msheiny authored and redshiftzero committed Jan 26, 2018
1 parent bdf075d commit d2e1ed4
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions molecule/aws/templates/junit.xml.j2
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
<testsuite errors="0" failures="{% if item.result|failed %}1{% else %}0{% endif %}" name="ansible" tests="1" time="0">
<testcase classname="high-level-test-runner-result" file="{{ item.file }}" name="{{ item.type }}" time="0">
<testsuite failures="0" errors="{% if item.result|failed %}1{% else %}0{% endif %}" name="ansible" tests="1" time="0">
<testcase classname="high-level-test-runner-result" file="{{ item.file }}" line="1" name="{{ item.type }}" time="0">
<system-out>{{ item.result.stdout|striptags }}</system-out>
<system-err>{{ item.result.stderr|striptags }}</system-err>
{% if item.result|failed %}<failure message="{{ item.type }} runner failed during execution phase"></failure>{% endif %}
{% if item.result|failed %}<error message="{{ item.type }} runner failed during execution phase">{{ item.result.stderr|striptags }}</error>{% endif %}
</testcase>
</testsuite>

0 comments on commit d2e1ed4

Please sign in to comment.