garbage in xml regress test

Pavel Stehule <pavel.stehule@gmail.com> writes:

When I checked result of xml test I found some strange lines in
expected/xml.out file
It is little bit strange - regress test reports ok, but diff is not empty

Probably your copy of libxml produces the results in xml_2.out instead.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

2016-08-07 23:16 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:

Pavel Stehule <pavel.stehule@gmail.com> writes:

When I checked result of xml test I found some strange lines in
expected/xml.out file
It is little bit strange - regress test reports ok, but diff is not empty

Probably your copy of libxml produces the results in xml_2.out instead.

no - it is in expected/xml.out

https://github.com/postgres/postgres/blob/master/src/test/regress/expected/xml.out

LINE 1: INSERT INTO xmltest VALUES (3, '<wrong');
^
DETAIL: line 1: Couldn't find end of Start Tag wrong line 1
<wrong
^

Regards

Pavel

Pavel Stehule <pavel.stehule@gmail.com> writes:

2016-08-07 23:16 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:

Probably your copy of libxml produces the results in xml_2.out instead.

no - it is in expected/xml.out

No, the output you're producing is in results/xml.out, but if the
regression test harness isn't complaining about it, it's because it
matches one of the available expected/xml*.out files. Which would
be xml_2.out, looks like.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

2016-08-08 5:44 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:

Pavel Stehule <pavel.stehule@gmail.com> writes:

2016-08-07 23:16 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:

Probably your copy of libxml produces the results in xml_2.out instead.

no - it is in expected/xml.out

No, the output you're producing is in results/xml.out, but if the
regression test harness isn't complaining about it, it's because it
matches one of the available expected/xml*.out files. Which would
be xml_2.out, looks like.

understand

Thank you

Pavel