[Octave-bug-tracker] [bug #53713] test failure "speed.m" in Octave 4.3.91

[Hartmut]

Follow-up Comment #2, bug #53713 (project octave):

This is the current version (4.3.91) of the problematic line in the tests of
speed.m:

[order, n, T_f1, T_f2] = speed ("sum (x)", "", [100, 1000], "v = 0; for i =
1:length (x), v += x(i); endfor");


On my Win7 PC it is NOT enough to increase the numbers to the following. This
still errors out after 18 seconds:

[order, n, T_f1, T_f2] = speed ("sum (x)", "", [100000, 110000], "v = 0; for i
= 1:length (x), v += x(i); endfor");


But those numbers do PASS the tests on my Win7 machine, but only after rougly
60 seconds:

[order, n, T_f1, T_f2] = speed ("sum (x)", "", [300000, 310000], "v = 0; for i
= 1:length (x), v += x(i); endfor");


Would it be OK to take the last code line for all OSes? This would increase
the run time of __run_test_suite__ by 1 minute for everybody. Or is it
necessary to split this tests up for different OSes (as also mentioned in the
FIXME text of speed.m)?



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53713>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/