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

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

[Octave-bug-tracker] [bug #39703] test script with two outputs doesn't r


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #39703] test script with two outputs doesn't run all tests
Date: Mon, 05 Aug 2013 23:34:34 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15

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

                 Summary: test script with two outputs doesn't run all tests
                 Project: GNU Octave
            Submitted by: sebald
            Submitted on: Mon 05 Aug 2013 11:34:33 PM GMT
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

I believe there might be a couple problems in test.m.  Here is the output of
running the test script on the "interpft.m" file:


>> [N_success, MAX_success] = test("interpft")
  ***** assert (max (abs (imag (interpft ([1:8], 20)))), 0, 2*eps);
!!!!! test failed
assert (max (abs (imag (interpft ([1:8], 20)))),0,2 * eps) expected
0
but got
   2.2542e-15
maximum absolute error 2.25417e-15 exceeds tolerance 4.44089e-16
shared variables
  scalar structure containing the fields:

    n =  11
    y =

       1.00000 + 1.00000i
       1.38397 + 1.38397i
       2.38397 + 2.38397i
       3.00000 + 3.00000i
       4.11603 + 4.11603i
       3.11603 + 3.11603i

N_success = 0
MAX_success = 0


>From the code in test.m, I believe that the test continues after a failure
only if in batch mode.  But there doesn't seem a way to control batch mode
from the option list; only by supplying an FID output argument.

However, one would think that the two output version should run all tests if
it is going to indicate now many were successful out of the total number of
tests.

Also, test.m is printing out shared variables in event of a failure.  Perhaps
there is some cruft left in the code:


      ## Show the variable context.
      if (! strcmp (__type, "error") && ! strcmp (__type, "testif")
          && ! all (__shared == " "))
        fputs (__fid, "shared variables ");
        eval (sprintf ("fdisp(__fid,bundle(%s));", __shared));
        fflush (__fid);
      endif


The shared variables that are listed are for a previous test and haven't
anything to do with the failed test, as far as I know.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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