[Octave-bug-tracker] [bug #51660] __run_test_suite__ can unwind its own return values

[Colin Macdonald]

URL:
  <http://savannah.gnu.org/bugs/?51660>

                 Summary: __run_test_suite__ can unwind its own return values
                 Project: GNU Octave
            Submitted by: cbm
            Submitted on: Fri 04 Aug 2017 06:59:42 PM UTC
                Category: Test Suite
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

__run_test_suite__.m does a lot of work inside both a unwind_protect and a try
block.  It later uses some of those variables which may have been unwound.

For example, "nfail".

Here's a kind of trivial example, but there may be more significant ones
(e.g., after some tests have run).

1.  Suppose I go to some dir where I do not have write permissions.

2.  Try:


>> [passed,failed] = __run_test_suite__ ({'somedir'}, {})

__run_test_suite__: could not open
/usr/share/octave/packages/symbolic-2.5.0/fntests.log for writing
error: 'nfail' undefined near line 143 column 12
error: called from
    __run_test_suite__ at line 143 column 10






    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/