Re: Jenkins build became unstable: FreeBSD_HEAD-tests2 #184

2014-11-04 Thread Garrett Cooper
On Nov 4, 2014, at 0:06, jenkins-ad...@freebsd.org wrote:

> See 

It appears that some of the new results from the libc testcases are causing 
Jenkins to crash in some cases:
- https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/186/testReport/

And it appears that kyua is creating “malformed XML” (invalid XML character) in 
others:
https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/184/testReport/junit/test-report/xml/_init_/

I’m not sure about the former case, but the latter case has to do with the fact 
that one of the testcases outputs invalid UTF-8 which is then turning up in the 
output. Even python complains about it:

% kyua report-junit > ~/report.junit
% python2 -c 'import os.path; import xml.dom.minidom as md; 
md.parse(os.path.expanduser("~/report.junit"))'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python2.7/xml/dom/minidom.py", line 1918, in parse
return expatbuilder.parse(file)
  File "/usr/local/lib/python2.7/xml/dom/expatbuilder.py", line 924, in parse
result = builder.parseFile(fp)
  File "/usr/local/lib/python2.7/xml/dom/expatbuilder.py", line 207, in 
parseFile
parser.Parse(buffer, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 27137, 
column 13

The problem testcase is lib.libc.locale.t_io:bad_big5_wprintf; once I remove 
that from the output, python no longer complains:

% python2 -c 'import os.path; import xml.dom.minidom as md; 
md.parse(os.path.expanduser("~/report.junit"))'

I fixed this issue in r274090.

Thank you!


signature.asc
Description: Message signed with OpenPGP using GPGMail


Jenkins build became unstable: FreeBSD_HEAD-tests2 #184

2014-11-04 Thread jenkins-admin
See 

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"