Martin Wille writes:
Joaquín Mª López Muñoz wrote:
Regression tests for Linux are updating OK every day, but the advanced developer and user reports seem to be stuck at Jul 5th.
The problem is a parse error produces by xsltproc while parsing test_results.xml in order to build extended_test_results.xml:
# Merging with expected results... # xsltproc -o /boost/head-regression/results/cs-Linux/extended_test_results.xml --param expected_results_file "'/boost/head-regression/etc/result-release-1_31_0.xml'" --param failures_markup_file "'/boost/head-regression/boost/status/explicit-failures-markup.xml'" "/boost/head-regression/boost/tools/regression/xsl_reports/xsl/add_expected_results.xsl" "/boost/head-regression/results/test_results.xml" /boost/head-regression/results/test_results.xml:4627: parser error : internal error pp(380): error in "trim_test": test bcs1 == LITERAL( "abcd" ) failed [L? ??? ?T? ^ /boost/head-regression/results/test_results.xml:4627: parser error : Extra content at the end of the document pp(380): error in "trim_test": test bcs1 == LITERAL( "abcd" ) failed [L? ??? ?T? ^
I've uploaded test_results.xml to http://tinyurl.com/2kxkl (3MB; gzipped). I've uploaded the related file test/test/basic_cstring_test.test/gcc-3.3.3-linux/debug/basic_cstring_test.output to http://tinyurl.com/2dkws (6K; text)
Aleksey, could you please check that out?
Looks like xsltproc can't handle certain ASCII characters that Python considers printable. Fixed in the CVS (in "report.py"). -- Aleksey Gurtovoy MetaCommunications Engineering