FOTS: fn:subsequence failing tests

[Sorin Marian Nasoi]

the following tests from the "fn-subsequence" test set take a very long time to finish.

Assigning to Matthias for redistribution.

   <test-case name="cbcl-subsequence-010">
      <description> Test subsequence on largest supported (non-infinite) range. </description>
      <created by="Oliver Hallam" on="2008-05-14"/>
      <test>count(subsequence(1 to 3000000000, -2147483648, 2147483647))</test>
      <result>
         <assert-string-value>0</assert-string-value>
      </result>
   </test-case>

   <test-case name="cbcl-subsequence-011">
      <description> Test unbounded subsequence with starting position out of int range. </description>
      <created by="Oliver Hallam" on="2008-05-14"/>
      <test>count(subsequence(1 to 3000000000, -2147483649))</test>
      <result>
 <assert-string-value>3000000000</assert-string-value>
      </result>
   </test-case>

   <test-case name="cbcl-subsequence-012">
      <description> Test unbounded subsequence with starting position out of int range. </description>
      <created by="Oliver Hallam" on="2008-05-14"/>
      <test>count(subsequence(1 to 3000000000, 2147483648))</test>
      <result>
 <assert-string-value>852516353</assert-string-value>
      </result>
   </test-case>

   <test-case name="cbcl-subsequence-013">
      <description> Test unbounded subsequence with largest allowed starting position. </description>
      <created by="Oliver Hallam" on="2008-05-14"/>
      <test>count(subsequence(1 to 3000000000, 2147483647))</test>
      <result>
         <assert-string-value>852516354</assert-string-value>
      </result>
   </test-case>

   <test-case name="cbcl-subsequence-014">
      <description> Test unbounded subsequence with largest allowed starting position. </description>
      <created by="Oliver Hallam" on="2008-05-14"/>
      <test>subsequence(1 to 3000000000, 2147483647, 5)</test>
      <result>
         <assert-string-value>2147483647 2147483648 2147483649 2147483650 2147483651</assert-string-value>
      </result>
   </test-case>

[Matthias Brantner (matthias-brantner)]

Just to make sure. Did you test with big integer support?

[Matthias Brantner (matthias-brantner)]

We should make sure that the tests give the right results before we submit the tests to the w3c. However, we shouldn't run them as part of the regression tests. The queries will just take long but they should generally work.

[Matthias Brantner (matthias-brantner)]

Executing each query takes approx. 7 minutes on my machine.

[Sorin Marian Nasoi (sorin.marian.nasoi)]

On my machine each test case takes 14 minutes after which it provides the correct result.

That is why the test cases that are not run because:
- the test case Seg Faults/HANGS (see "re00975", "re00976", "re00976a", "fn-unparsed-text-lines-052")
- the test case takes a very long time to run (see "cbcl-subsequence-011", "cbcl-subsequence-012", "cbcl-subsequence-013", "cbcl-subsequence-014")
are reported as "notRun".

"notRun" is a valid value according to the
http://dev.w3.org/cvsweb/2011/QT3-test-suite/FOTSResults.xsd?rev=1.2;content-type=text%2Fplain
part "resultStatusType".

When we report the results to W3C we should mark the test cases that take a long time but give the correct result as "PASS" instead of "notRun".

[Sorin Marian Nasoi (sorin.marian.nasoi)]

The reported tests are already marked as SLOW QUERIES in CTest also that is why I am marking this issue as FIX RELEASED.