Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Possible bug with XML results output
Options
Previous Topic Next Topic
Phonesis
#1 Posted : Tuesday, April 19, 2016 8:29:12 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 4/14/2016(UTC)
Posts: 32
Location: United Kingdom

Was thanked: 3 time(s) in 3 post(s)
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.
Back to top
Remco
#2 Posted : Tuesday, April 19, 2016 11:05:18 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,216

Thanks: 975 times
Was thanked: 1303 time(s) in 1208 post(s)
Interesting, thanks for letting me know about this one. I'll make a note to get it fixed.
Back to top
Phonesis
#3 Posted : Tuesday, April 19, 2016 11:21:20 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 4/14/2016(UTC)
Posts: 32
Location: United Kingdom

Was thanked: 3 time(s) in 3 post(s)
Originally Posted by: Remco Go to Quoted Post
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.
Back to top
1 user thanked Phonesis for this useful post.
Remco on 4/19/2016(UTC)
Phonesis
#4 Posted : Wednesday, April 20, 2016 10:49:32 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 4/14/2016(UTC)
Posts: 32
Location: United Kingdom

Was thanked: 3 time(s) in 3 post(s)
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.
Back to top
Remco
#5 Posted : Wednesday, April 20, 2016 12:21:11 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,216

Thanks: 975 times
Was thanked: 1303 time(s) in 1208 post(s)
I'll see if I can squeeze it into the 2.21 release due this week.
Back to top
Phonesis
#6 Posted : Wednesday, April 20, 2016 2:25:43 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 4/14/2016(UTC)
Posts: 32
Location: United Kingdom

Was thanked: 3 time(s) in 3 post(s)
Great! Thanks Remco
Back to top
Remco
#7 Posted : Friday, April 22, 2016 3:23:29 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,216

Thanks: 975 times
Was thanked: 1303 time(s) in 1208 post(s)
A fix for this issue is now available in v2.21, released today - http://www.ncrunch.net/download
Back to top
1 user thanked Remco for this useful post.
samholder on 5/10/2016(UTC)
Phonesis
#8 Posted : Friday, April 22, 2016 9:40:11 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 4/14/2016(UTC)
Posts: 32
Location: United Kingdom

Was thanked: 3 time(s) in 3 post(s)
Originally Posted by: Remco Go to Quoted Post
A fix for this issue is now available in v2.21, released today - http://www.ncrunch.net/download



Great work Remco. Thanks very much.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.056 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download