[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49470] [MXE] eig.cc-tst failure in __run_test
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #49470] [MXE] eig.cc-tst failure in __run_test_suite__.m with 64-bit-Octave |
Date: |
Wed, 2 Nov 2016 15:56:48 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #9, bug #49470 (project octave):
These tests are a new addition in this cset:
changeset: 22305:510886d03ef2
user: Barbara Locsi <address@hidden>
date: Tue Aug 16 02:07:58 2016 +0100
summary: eig: new options for choice of algorithm, balancing, and output
(patch #8960)
I've added Barbara to the CC list for this bug. Maybe she knows why the tests
were written in this manner.
It seems odd to me that is_qz_accurate and is_chol_accurate are always either
true or false. Won't this depend on the actual HW/SW system? There is no
prior test that would make these values dependent on the actual platform
Octave is being used on.
One way around this, as Avinoam suggests, is to compare with a tolerance in
assert, rather than using isequal which requires absolute equality.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49470>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/