[Octave-bug-tracker] [bug #54718] __run_test_suite__ doesn't preserve start or working directory

[Mike Miller]

Follow-up Comment #6, bug #54718 (project octave):

After some more testing, the following is enough to reproduce this for me 100%
in the development version:


tdir = __octave_config_info__ ("octtestsdir");
__run_test_suite__ ({fullfile(tdir, "libinterp", "corefcn")}, {})


With any other directory or set of directories, when '__run_test_suite__'
finishes it correctly restores the working directory. If and only if the
libinterp/corefcn directory is included in the test run, then the working
directory is set to that directory at the end.

If I pass the path(s) to Octave 4.4.1's test directory(ies), even if I am
running Octave 5, the working directory is restored correctly.

I put a debug print into the unwind_protect_cleanup block where the working
directory is supposed to be restored, and it does execute the block of code,
and says it is calling 'cd' with the right argument. But yet, when the
function returns, the working directory is not what was passed to 'cd'.

One final clue. If I disable the setting in the Preferences, File Browser
dialog that says "Synchronize Octave working directory with file browser",
then the working directory *is* restored to the correct original directory.
But again, this only seems to be a problem with the libinterp/corefcn
directory.

Can anyone verify any or all of these findings?

    _______________________________________________________

Reply to this item at:

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

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