Support #5173
closed
Certain XQuery update operations seem to be failing with Saxon 10
100%
Description
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:
http://www.example.com/hisco
but now produce an empty string.
Related issues
Updated by Michael Kay over 2 years ago
We do routinely run the XQuery Update tests, and they're all passing, so there must be some difference in the way that you run them from the way that we do. We'll need to find some way of reproducing the failure conditions.
Updated by Michael Kay over 2 years 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 Michael Kay over 2 years ago
This is a duplicate of bug #4974, which I had previously decided not to fix on the 10.x branch. I'll reopen it and review that decision.
Updated by Radu Coravu over 2 years 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.
Updated by Michael Kay over 2 years ago
- Is duplicate of Bug #4974: XQuery Update: namespace propagation is not working added
Updated by Michael Kay about 2 years ago
- Status changed from New to Resolved
The fix has now been retrofitted to the Saxon 10.x branch.
Note that this involves changes to some methods in the MutableNodeInfo interface, so it could be disruptive.
Updated by Debbie Lockett about 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Applies to branch 10 added
- Fix Committed on Branch 10 added
- Fixed in Maintenance Release 10.7 added
See bug #4974 status: fix applied in the Saxon 10.7 maintenance release.
Please register to edit this issue
.