Testsuite failures in today's CVS



I just did a cvs update and built maxima on a linux box using clisp.
The build went without complaint, but there were two testsuite failures
that I don't recall seeing before:

Running tests in rtest15: 
********************** Problem 35 ***************
Input:
          sin(3 a)
trigrat(------------)
            %pi
        sin(--- + a)
             3


Result:
error-catch

This differed from the expected result:
- 1 + cos(2 a) + sqrt(3) sin(2 a)

********************** Problem 36 ***************
Input:
    2         2 - %pi
sin (3 a) sin (----- + a + b)
                  3
(-----------------------------
            2     %pi
         sin (a - ---)
                   3
                                - %pi
   2 sin(a) sin(3 a) cos(b) sin(----- + a + b) sin(3 a + 3 b)
                                  3
- ----------------------------------------------------------
                            %pi
                    sin(a - ---) sin(a + b)
                             3
      2       2
   sin (a) sin (3 a + 3 b)
+ -----------------------, result : trigrat(%%), 
            2
         sin (a + b)
expected : (- (- 9 + 10 cos(2 a) - 2 sqrt(3) sin(2 a) - cos(4 a)
+ sqrt(3) sin(4 a) + 10 cos(2 b) - 2 sqrt(3) sin(2 b) - cos(4 b)
+ sqrt(3) sin(4 b) - 4 cos(2 b - 2 a) - 8 cos(2 a + 2 b)
+ 4 sqrt(3) sin(2 a + 2 b) + 2 cos(4 a + 2 b) - 2 sqrt(3) sin(4 a + 2 b)
+ 2 cos(2 a + 4 b) - 2 sqrt(3) sin(2 a + 4 b) - cos(4 a + 4 b)
+ sqrt(3) sin(4 a + 4 b)))/4, ratsimp(result - expected))


Result:
error-catch

This differed from the expected result:
0

Caused an error break: rtest15


I also tried running one of the cases manually:

(%i2) sin(3*a)/(sin(%pi/3+a));
                                   sin(3 a)
(%o2)                            ------------
                                         %pi
                                 sin(a + ---)
                                          3
(%i3) trigrat(%);
Maxima encountered a Lisp error:


EVAL: variable <<<<<<< has no value

Automatically continuing.
To reenable the Lisp debugger set *debugger-hook* to nil.