[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50235] return code is zero, even if there was
|
From: |
John W. Eaton |
|
Subject: |
[Octave-bug-tracker] [bug #50235] return code is zero, even if there was an error |
|
Date: |
Wed, 8 Feb 2017 19:26:20 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #3, bug #50235 (project octave):
Yes, we probably should have tests for this kind of thing. Can we do it
reasonably within the existing test framework, or is this something we should
do with a shell script? Is a shell script sufficient? I think it should be
because we don't really need to worry about continuing after a test failure
that causes a segfault, for exmaple.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50235>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/