9130 2010-02-23 16:22:04 +0000 XQTS:CVS: errors-and-optimization-1, 6 2010-09-08 10:11:10 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite unspecified PC Windows NT CLOSED FIXED P2 normal --- 1 tim jonathan.robie nick public-qt-comments oldest_to_newest 32587 0 tim 2010-02-23 16:22:04 +0000 errors-and-optimization-1 is marked in the catalog as expecting a runtime error. The query contains a type error (XPTY0004). The catalog entry has no expected-error element. errors-and-optimization-6 contains a static error (XPST0017) - fn:QName expects two arguments. The catalog lists it as expecting FOCA0002 (: Name: errors-and-optimization-6.xq :) (: Description: Expressions must not be rewritten in such a way as to create or remove static errors. :) (: insert-start :) (: insert-end :) let $s := "var:QName" return QName($s) 33950 1 jonathan.robie 2010-03-26 17:05:58 +0000 I have checked in result files for queries 1 and 3 - was 6 the right number here? 34654 2 nick 2010-04-08 12:46:07 +0000 Yes. There was a change required for 6. 34655 3 nick 2010-04-08 12:47:02 +0000 errors-and-optimization-1 also now has a spurious newline at the end of the result. 37231 4 jonathan.robie 2010-08-04 18:07:27 +0000 Fixed the error for errors-and-optimization-6 - it now expects XPST0017. 37372 5 tim 2010-08-12 15:19:30 +0000 Thanks. errors-and-optimization-6 is fixed, but errors-and-optimization-1 remains in error. See Comment 3. 37594 6 tim 2010-08-18 08:28:35 +0000 errors-and-optimization-6 is incorrectly marked in the catalog as is-XPath2="true". 38570 7 jonathan.robie 2010-09-07 22:35:30 +0000 (In reply to comment #5) > Thanks. > > errors-and-optimization-6 is fixed, but errors-and-optimization-1 remains in > error. OK, I've removed the extraneous newline now. 38571 8 jonathan.robie 2010-09-07 22:36:55 +0000 (In reply to comment #6) > errors-and-optimization-6 is incorrectly marked in the catalog as > is-XPath2="true". I modified it so it runs as either XQuery or XPath: for $s in "var:QName" return QName($s) 38651 9 tim 2010-09-08 10:10:45 +0000 I can confirm that this is now fixed. Thanks.