[Octave-bug-tracker] [bug #57584] spurious test "FAIL"s when running test suite in Octave with "--traditional" startup parameter

[Mike Miller]

Follow-up Comment #13, bug #57584 (project octave):

> first checking to see whether there is some bug uncovered by the test when
running with the option.

Sure, that's certainly worth doing for someone with the motivation. There are
quite a few test failures with just disable_range set. For example,
libinterp/dldfcn/amd.cc has one test failure because


>> disable_range (false)
>> zeros (1, 0)
ans = [](1x0)
>> disable_range (true)
>> zeros (1, 0)
ans = [](0x0)
>> test libinterp/dldfcn/amd.cc 
***** testif HAVE_AMD
 assert (amd ([]), zeros (1,0))
!!!!! test failed
ASSERT errors for:  assert (amd ([]),zeros (1, 0))

  Location  |  Observed  |  Expected  |  Reason
     .          O(1x0)       E(0x0)      Dimensions don't match



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57584>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/