[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57584] spurious test "FAIL"s when running tes

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #57584] spurious test "FAIL"s when running test suite in Octave with "--traditional" startup parameter
Date: Wed, 15 Jan 2020 22:22:27 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36

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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]