octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54718] __run_test_suite__ doesn't preserve st


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #54718] __run_test_suite__ doesn't preserve start or working directory
Date: Mon, 24 Sep 2018 18:11:20 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Update of bug #54718 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #4:

I can confirm on Debian with 2da65009cc7f.

1. I tested in the GUI, and when '__run_test_suite__' finishes successfully,
the current directory is now
${OCTAVE_HOME}/share/octave/5.0.0/etc/tests/libinterp/corefcn.

2. I tested in octave-cli

3. Yes, the GUI shows the local directory changing as the test directories are
iterated over. It has always been this way. It's only the workspace panel that
does not update when a script runs. I believe there is a user preference to
not update directory displayed on the GUI when the current directory changes
in the interpreter.

4. I think this is a regression, and possibly due to one of the "fixed" test
scripts that has changed or been added since 4.4. I will do some more testing
to see if I can verify that or narrow it down further. I can only guess,
because I _think_ I saw the correct directory flashing in the GUI toolbar, up
until the test suite got to the fixed tests.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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