[Octave-bug-tracker] [bug #59343] [octave forge] (symbolic) `pkg test symbolic` fails in "sympref.m"

[Markus Mützel]

URL:
  <https://savannah.gnu.org/bugs/?59343>

                 Summary: [octave forge] (symbolic) `pkg test symbolic` fails
in "sympref.m"
                 Project: GNU Octave
            Submitted by: mmuetzel
            Submitted on: Sat 24 Oct 2020 10:59:18 PM CEST
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.0.92
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

When running the BISTs of symbolic 2.9.0 in Octave 6.0.92, the tests for
"sympref.m" fail with the following error:

>>>>> processing C:\Program Files\GNU
Octave\Octave-6.0.92\mingw64\share\octave\packages\symbolic-2.9.0\sympref.m
***** test
 sympref('ipc', 'systmpfile');
 syms x
 delete('tmp_python_cmd.py')
!!!!! test failed
fprintf: invalid stream number = -1
shared variables   scalar structure containing the fields:

    sympref_orig =

      scalar structure containing the fields:

        ipc = default
        display = ascii
        digits = 32
        quiet = 0

***** error <line 1> pycall_sympy__ ('raise ValueError')
!!!!! error failed.
Expected <line 1>, but got <fprintf: invalid stream number = -1>

***** error <line 1> pycall_sympy__ ('raise ValueError', struct('a', 1, 'b',
'word'))
!!!!! error failed.
Expected <line 1>, but got <fprintf: invalid stream number = -1>


This is probably because the current directory during the test is the
directory of the .m file. The user might not have write permission for that
directory (without elevated or superuser privileges). Could the current
directory be changed to `tempdir ()` for these tests?

I've marked as Microsoft Windows because I've tested on that OS. But I believe
the error would also happen on Linux if the package is installed in /usr and
Octave runs without superuser privileges.

CC'ing Colin Macdonald as the package maintainer.





    _______________________________________________________

Reply to this item at:

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

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