Re: testing install of suitesparse

[Ben Abbott]

On Oct 24, 2007, at 7:54 PM, John W. Eaton wrote:

> On 24-Oct-2007, Ben Abbott wrote:
>
> | You're correct. I checked the fntests.log and found the ismember.m
> | did report an error. However, since the proper response was  
> given, it
> | appears to be a false failure.
> |
> |  >>>>> processing /Users/bpabbott/src/octave/07.10.12/scripts/set/
> | ismember.m
> |    ***** xtest assert (ismember ('', {'abc', 'def'}), false);
> | !!!!! known failure
> | error: assert (ismember (, {"abc", "def"}),false) expected
> | 0
> | but got
> | [](0x0)
> | Dimensions don't match
> |    ***** xtest fail ('ismember ([], {1, 2})', 'error:.*');
> | !!!!! known failure
> | error: expected error <error:.*> but got none
>
> I don't understand what you mean by "false failure".  In both of the
> cases above, what ismember actually does is different from what we
> would like it to do.
>
> jwe

Perhaps my inferred understanding of the test is lacking, but it  
appears to me that ismember('',{'abc','def'}) produced [](0x0) ... as  
it should. However, the message indicates an "expected" result of 0.

This is further complicated by the phrase: "error: expected error  
<error:.*> but got none" ... reminds me of a professor I had who  
flunked me because he was certain I wasn't capable of the A's I'd  
scored on his tests ;-)

In any event, perhaps, my qualification, "false failure", is  
improper, but I don't understand why a correct answer to a test  
produces an error.

Ben