[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: Hartmut
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:39 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0

Follow-up Comment #9, bug #57584 (project octave):

@Markus: No, I think there hasn't been any action on Mike's comment #3.

I would summarize and divide up this bug report in three seperate issues:

* A failure of a unit test in the publish function. This issue is already
dealt with in bug #57439 (see comment #8).

* A misbehavior of the run_test_suite command, reporting failing test
different on the screen output than in the log file. This issue was my
original intention of this bug report (see my comment #0 and comment #2). But
this was an error on my side, I would now say we can close this issue as
"works for me".

* Actually failing unit tests, when Octave is running with the traditional
startup option. There seem to be at least 125 of them. Mike had a look at them
(see his comment #3 and comment #1). And they seem to all fail for a good
reason, for example because they are using an Octave feature that was
intentionally switched off by the traditional startup option. For this one
there seem to be different ways "forward":
** Just let it stay as it is now. (My personal favorite). Those tests fail for
a good reason, because someone started Octave with non-standard options.
** Change all (at least 125) unit tests, so that they will not run when the
respective startup option was used that disabled an essential Octave feature
that they need. Something like "missing feature" unit tests.
** Change the run_test_suite command, so that it issues a generic message like
"some tests mail fail to the the current setting of the parameters X and Y".
(my second favorite, and also one of Mike's in commment #3.)
** Change the run_test_suite command, so that always the standard options of
Octave are used. (I think this would not be good, then the tests I was trying
to do where not even possible.)

I will leave my "fingers away" from this bug report, now. My original
intention is fulfilled. And for the (maybe) open questions I am not enough
into the Octave code.


Reply to this item at:


  Message sent via Savannah

reply via email to

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