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

[Andrew Janke]

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

> exit the GUI, re-launch the GUI, run test 
> exit the GUI, re-launch the GUI, run test 
> exit the GUI, re-launch the GUI, run test 

Did this. The failure did not appear. Sounds like there might be a
GUI-session-scoped cleanup happening, as you suspect.

Another weird thing: Running just `file-io.cc-tst` on its own repeatedly in
the GUI does not cause this failure:


>> cd
/Applications/Octave-4.4.0.app/Contents/Resources/usr/Cellar/octave-octave-app_4.4.0/4.4.0/share/octave/4.4.0/etc/tests/libinterp/corefcn
>> test file-io.cc-tst
PASSES 90 out of 90 tests
>> test file-io.cc-tst
PASSES 90 out of 90 tests
>> test file-io.cc-tst
PASSES 90 out of 90 tests
>> test file-io.cc-tst
PASSES 90 out of 90 tests
>> test file-io.cc-tst
PASSES 90 out of 90 tests
>> test file-io.cc-tst
PASSES 90 out of 90 tests



    _______________________________________________________

Reply to this item at:

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

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