[Octave-bug-tracker] [bug #57584] spurious test "FAIL"s when running test suite in Octave with "--traditional" startup parameter

[Mike Miller]

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:

  <https://savannah.gnu.org/bugs/?57584>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/