[py-dev] [hpk42/pytest] stdout and stderr double-encoded in junitxml (issue #178)

[Jason R . Coombs]

--- you can reply above this line ---

New issue 178: stdout and stderr double-encoded in junitxml
https://bitbucket.org/hpk42/pytest/issue/178/stdout-and-stderr-double-encoded-in

Jason R. Coombs:

I'm finding that the junit XML generated by pytest 2.2.4 gets double-encoded 
output. For example, here's a snippet from one run:

{{{
<failure>... Error in parsing

gryphon/models/qsl.py:63: QSLError</failure><system-err>Message 1
{&amp;apos;exception&amp;apos;: [&amp;apos;ParseError: Both inline and named res
ponse lists were used for question lookahead\n&amp;apos;],
 &amp;apos;message&amp;apos;: [&amp;apos;ParseError: Both inline and named respo
nse lists were used for question lookahead\n&amp;apos;],
 &amp;apos;status&amp;apos;: 500,
...
}}}

The stderr stream for that looks something like:

{{{
Message 1
{'exception': ['ParseError: Both inline and named response lists were used for 
question lookahead\n'],
 'message': ['ParseError: Both inline and named response lists wer eused for 
the queston lookahead\n'],
 'status': 500,
}}}

Notice that the tickmarks are being escaped for XML (to &apos;) and then again 
the ampersand is getting escaped to &amp;apos;.


--

This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.
_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev