[Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice

[Dan Sebald]

Follow-up Comment #3, bug #54180 (project octave):

Thanks; that helps narrows things down.

Running file-io.cc-tst on its own repeated without error is a clue...  I've
managed to isolate and repeat the third case you cited.  The slightly more
verbose result is


>> test file-io.cc-tst
ans =
{
  [1,1] = [](0x1)
}

***** error textscan (single (40))
!!!!! error failed.
Expected an error, but got no error


So this example is expecting textscan (single (40)) to fail, but it isn't
failing.  That suggests to me that some test *after* file-io.cc-tst is opening
a bunch of file, all the way up to file ID "40", without closing that file
(probably many files).  Since file-io.cc-tst on its own is not failing, we
need to find that later test which is opening files but not closing them.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54180>

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