This is pretty obscure but came across it last night during a test run. Some tests were timing out (exceeding the NCrunch timeout limit which I set for 5 mins)
As a result of this, the NCrunch NUnit XML report and RawResults XML reports seem to be broken due to the following lines being within the XML:
at nCrunch.TestExecution.TestRunnerThread.ETX()
at nCrunch.TestExecution.TestRunnerThread.STX()
These lines only appear when a test times out and exceeds the NCrunch limit as it's part of the logging you get when that occurs I think.
The XML is invalid according to Chrome and FireFox but oddly loads in IE. After playing around, I discovered it appears to dislike ETX and STX and treats them as illegal characters. Not sure why.
IE strips them out by looks of it and the XML reports load fine.
Remco NCrunch Developer
#8621
19 Apr 2016 11:05 UTC
Interesting, thanks for letting me know about this one. I'll make a note to get it fixed.
Remco wrote:Interesting, thanks for letting me know about this one. I'll make a note to get it fixed.
Looks like it's treating it as an end of line character. The chrome error returned is:
error on line 1789 at column 33: Input is not proper UTF-8, indicate encoding !
Bytes: 0x03 0x28 0x29 0x0A
This appears to refer to the ETX segment.
Thanks for looking into this. I don't suppose you have any idea on when a fix might be out? Also, will it come in the form of an update to the NCrunch.exe console tool?
We query TeamCity via a REST request once the run completes and get the RawResults.xml contents to then determine what tests have failed. With this issue, it prevents us from reading the XML. Have tried amending the invalid byte arrays (0x03, 0x02) to something else (0x056) and then converting it back to XML but for some reason the TeamCity API then throws a 400 bad request whenever we try to do a POST with that modified content.
We query TeamCity via a REST request once the run completes and get the RawResults.xml contents to then determine what tests have failed. With this issue, it prevents us from reading the XML. Have tried amending the invalid byte arrays (0x03, 0x02) to something else (0x056) and then converting it back to XML but for some reason the TeamCity API then throws a 400 bad request whenever we try to do a POST with that modified content.
Remco NCrunch Developer
#8626
20 Apr 2016 12:21 UTC
I'll see if I can squeeze it into the 2.21 release due this week.
Great! Thanks Remco
Remco NCrunch Developer
#8642
22 Apr 2016 03:23 UTC
A fix for this issue is now available in v2.21, released today - http://www.ncrunch.net/download
Remco wrote:A fix for this issue is now available in v2.21, released today - http://www.ncrunch.net/download
Great work Remco. Thanks very much.
Post a reply
Log in to reply.