[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 15:30:51 -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 #10, bug #57584 (project octave):

No actions have been taken yet.

My suggestions are

* do nothing, or
* add code to __run_test_suite__.m that forces certain settings to _undo_ what
--traditional does (for example, disable_range(false)), and restore them at
the end of the function, or
* add warnings to __run_test_suite__.m if any of the --traditional settings
are set, that certain tests may fail and that should not be considered a bug.

Any changes to __run_test_suite__.m that change or check these settings
further make this function specific to the Octave test suite, not a general
purpose test runner as some people use it for.

My preference would be to do nothing, and just document somewhere or make it
clear when it comes up that the test suite is not expected to work fully under
--traditional behavior settings.


Reply to this item at:


  Message sent via Savannah

reply via email to

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