#129 Test rtestode fails if run after rtest3

closed
nobody
Lisp Core (472)
5
2014-08-21
2002-09-20
No

I have added a new test file tests/rtestode.mac.
If it is run after rtest3.mac, several tests fail.

For example:
/* ********************** Problem 11. *************** */
%Input is
2
ODE2(x y COS(x y) + SIN(x y) + x COS(x y) y = 0, y,
x)

    x

The result is
/
[
x SIN(x y) + I 0 dy = %C
]
/

Using ratsimp
Using ratsimp
This differed from the expected result:
x SIN(x y) = %C

Discussion

  • Logged In: YES
    user_id=365569

    I have generated a reduced case. Running the two line
    rtest3.mac before the four line rtestode.mac ends in failure.

    How does one undo a DECLARE(INTEGRATE,NOUN); ?

    /* rtest3.mac */
    DECLARE(INTEGRATE,NOUN);
    DONE$

    /* rtestode.mac */
    kill(all);
    done;
    ode2(x^2*cos(x*y)*'diff(y,x) + (sin(x*y)+x*y*(cos(x*y)))=0, y,
    x);
    x*sin(x*y)=%C;

    ##### Test output ###

    Testing rtestode.mac
    /* ********************** Problem 1. *************** */
    %Input is
    KILL(ALL)

    The result is
    DONE

    ..Which was correct
    /* ********************** Problem 2. *************** */
    %Input is
    2 dy
    ODE2(x y COS(x y) + SIN(x y) + x COS(x y) -- = 0, y, x)
    dx

    The result is
    /
    [
    x SIN(x y) + I 0 dy = %C
    ]
    /

    Using ratsimp
    Using ratsimp
    This differed from the expected result:
    x SIN(x y) = %C

    The number of differences found was 1 in problems: (2)
    Error summary:
    Error(s) found in rtestode.mac: (2)

     
  • Robert Dodier
    Robert Dodier
    2005-08-22

    • status: open --> closed
    • labels: --> Lisp Core
     
  • Robert Dodier
    Robert Dodier
    2005-08-22

    Logged In: YES
    user_id=501686

    Appears to be fixed by revision of kill in r1.22
    src/suprv1.lisp (2005/04/03). Maxima 5.9.1 official release
    on cmucl 19a and 5.9.1cvs on clisp 2.31, build date
    2005/03/31, both show this bug. 5.9.1cvs on clisp 2.33 and
    on gcl 2.6.6, build date 2005/08/21, do not show it. Closing
    this bug as fixed.