[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: Sun, 12 Jan 2020 16:48:41 -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 #3, bug #57584 (project octave):

I ran Octave with --traditional, and then reset disable_diagonal_matrix,
disable_permutation_matrix, and disable_range all back to false, and ran the
test suite. In this configuration, I only got 4 test failures, so most of
these failures are due to the assumptions of the diagonal, permutation, and
range special array types.

The 4 remaining failures:

* savefig.m - test fails because --traditional sets 'save_default_options' to
'-mat-binary', which breaks saving figures to a file
* parser.tst - test fails because it expects the "Matlab-style short-circuit
operation" warning, but that warning is disabled with --traditional
* publish.tst - tests failed with "__imwrite__: invalid function handle", may
not be related to --traditional at all, may be a plot system race condition

A sensible way forward might be to either set these options to expected values
at the start of the test suite, or to error out with a message to the user
that these --traditional options change the behavior of Octave sufficiently
that the test suite isn't reliable.


Reply to this item at:


  Message sent via Savannah

reply via email to

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