AFAIK Zorba does not support StaticTyping. That is why the StaticTyping tests should be marked as expected failures.
There is only one test that has to be looked at from this list test/rbkt/w3c_testsuite/XQueryX/Construct/ComputeCon/ComputeConAttr/K2-ComputeConAttr-35 If the intended purpose was to make sure the XQueryX expected failures are up to date than this indeed is an issue that should be checked. ** Summary changed: - XQTS failures due to W3C bugs + XQTSX failures due to W3C bugs -- You received this bug notification because you are a member of Zorba Coders, which is the registrant for Zorba. https://bugs.launchpad.net/bugs/867094 Title: XQTSX failures due to W3C bugs Status in Zorba - The XQuery Processor: New Bug description: The following XQTS are marked as expected failures due to W3C bugs: test/rbkt/w3c_testsuite/XQueryX/Construct/ComputeCon/ComputeConAttr/K2-ComputeConAttr-35 test/rbkt/w3c_testsuite/XQueryX/StaticTyping/STPathExpr/STSteps/STAxes/ST-Axes011 test/rbkt/w3c_testsuite/XQueryX/StaticTyping/STPathExpr/STSteps/STAxes/ST-Axes012 test/rbkt/w3c_testsuite/XQueryX/StaticTyping/STPathExpr/STSteps/STAxes/ST-Axes013 test/rbkt/w3c_testsuite/XQueryX/StaticTyping/STPathExpr/STSteps/STAxes/ST-Axes014 test/rbkt/w3c_testsuite/XQueryX/StaticTyping/STPathExpr/STSteps/STAxes/ST-Axes015 This is a tracking bug so that we can mark them as expected failures in our system. When/if the corresponding W3C bugs are resolved, this bug should be updated. Assigning to Sorin as the master of W3C conformance. To manage notifications about this bug go to: https://bugs.launchpad.net/zorba/+bug/867094/+subscriptions -- Mailing list: https://launchpad.net/~zorba-coders Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~zorba-coders More help : https://help.launchpad.net/ListHelp