This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following tests use optional feature FTMildNot but do not expect FTST0001 FTWindow-complexwords4 FTDistance-complexwords4 unconstrained-examples-353-1 FTMildNot-unconstrained-q1 FTMildNot-unconstrained-q2 FTMildNot-unconstrained-expr1 FTMildNot-unconstrained-and1 FTMildNot-unconstrained-and2 FTMildNot-unconstrained-or1 FTMildNot-unconstrained-or2 FTMildNot-unconstrained-not1 FTWindow-unconstrained-complexwords4 FTDistance-unconstrained-complexwords4 FTDistance-unconstrained-complexexpr1 FTDistance-unconstrained-complexexpr2 FTDistance-unconstrained-complexexpr3 logical-queries-results-q7 logical-queries-results-q7b
Tests under the optional section of the testsuite do not expect the error on purpose (this certainly includes all the xx-unconstrained tests; I'd need to look at the others): they are specifically testing implementation of the optional feature.
Thanks. It might be worth mentioning this in the guidelines for running the test suite.
Of these tests, the following do not appear in the FTMildNotUnconstrained optional test group and so require attention. FTWindow-complexwords4 FTDistance-complexwords4 FTWindow-unconstrained-complexwords4 FTDistance-unconstrained-complexwords4 FTDistance-unconstrained-complexexpr1 FTDistance-unconstrained-complexexpr2 FTDistance-unconstrained-complexexpr3 logical-queries-results-q7 logical-queries-results-q7b
Done.
Confirmed fixed.