Closed
Description
Originally reported by: Anonymous
We have tests that wrap a binary tool in pexpect. If there is a problem with the test and we get a pexpect traceback where the junit results contain some xml characters that cause Jenkins junit reporter to fail and consequently not report results.
The culprit is "^[" (0x1b) that doesn't seem to be filtered out by pytest.
E 0: re.compile("Test threads created successfully")
E buffer (last 100 chars):
E before (last 100 chars): CANCEL) on thread 19, slot 1, serial number 1850653014!^M
E **^[**[0m^M
E ^M
E Waiting for threads to terminate.^M
E
E after: <class 'pexpect.EOF'>
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
pytestbot commentedon Feb 26, 2013
Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):
found the problem, the valid character ranges need a review, there is a invalid area in a range we have as valid in the code
pytestbot commentedon Feb 26, 2013
Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):
i have to revise the problem
the character codes are actually correct, but we write them out in a incorrect encoding
pytestbot commentedon Feb 26, 2013
Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):
seems we dont, i missed the encoded file, but now the behaviour pretty much does not make sense,
pytestbot commentedon Nov 25, 2013
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
Ronny, any chance you can resolve this issue until thursday?
pytestbot commentedon Dec 10, 2013
Original comment by Anatoly Bubenkov (BitBucket: bubenkoff, GitHub: bubenkoff):
wasn't able to reproduce the issue
please have a PR reproducting in the test (test_invalid_xml_escape)
Merged in yield-experimental-docs (pull request #267)