Certain XQuery update operations seem to be failing with Saxon 10
We have an auto test which takes these operations: https://dev.w3.org/2007/xquery-update-10-test-suite/
and runs them with Saxon.
The following scripts:
xqTestSuite\Queries\XQuery\InsertExpressions\id-insert-expr-086.xq xqTestSuite\Queries\XQuery\ReplaceExpressions\id-replace-expr-045.xq xqTestSuite\Queries\XQuery\ReplaceExpressions\id-replace-expr-045-no-inherit.xq xqTestSuite\Queries\XQuery\RenameExpressions\id-rename-expr-033.xq xqTestSuite\Queries\XQuery\RenameExpressions\id-rename-expr-034.xq xqTestSuite\Queries\XQuery\RenameExpressions\id-rename-expr-033-no-inherit.xq xqTestSuite\Queries\XQuery\RenameExpressions\id-rename-expr-034-no-inherit.xq
when run over an empty XML document used to produce in the output file with Saxon 9 the string:
but now produce an empty string.
Updated by Michael Kay 9 months ago
I think I may have found the problem. The test is returning an empty sequence, which leads to the test driver
not writing any result file, which means that the comparison is done with the saved results from a previous run, that is, the results from the last time the test succeeded writing an empty results file; we get an
ArrayIndexOutOfBoundsException looking at the empty file to see if it starts with a BOM, and we ignore this exception taking us down the success path.
More recently we have integrated the XQuery Update tests into the main qt3 test suite, using assertions rather than file comparison to test the results. I'm not sure if the new version gets run on the Saxon 10 branch, I will need to check.
Updated by Radu Coravu 9 months ago
Great thank you Michael. I will keep adding all my observations as support requests as I do not know exactly what is bug and what is intended change decision. This problem does not influence us much, it's just an observation based on that failed auto test.
Please register to edit this issue