Test suite failure after updating from git



On 06/14/2013 06:08 PM, Robert Dodier wrote:
> On 2013-06-14, Paul Bowyer <pbowyer at olynet.com> wrote:
>
>> build_info(version="branch_5_30_base_108_gc56c120",timestamp="2013?06?14
>> 11:08:18",
>> host="x86_64?unknown?linux?gnu",lisp_name="SBCL",lisp_version="1.1.7")
>> Running tests in rtest6:
>> ********************** Problem 9 ***************
>> Input:
>> block([a,L],a:make_array(fixnum,3),L:buildq([a],lambda([x],a[x])),print(L,L(0)))
>> Result:
>> error?catch
>> This differed from the expected result:
>> 0
> Hmm -- I don't get that error. I am working w/ SBCL 1.0.55, also Clozure
> CL 1.9, and Clisp 2.49 with current source code on Ubuntu (32 bit).
> I wonder if it makes a difference that you have 64 bit Linux.
>
> best
>
> Robert Dodier
>
> _______________________________________________
> Maxima mailing list
> Maxima at math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima
Hi Robert:

I was using the same lisp with the previous version of Maxima, which was 
also downloaded from git.

In my cloned git repository of Maxima, not knowing a lot about git, I 
added a branch named pfb-build and did a git checkout pfb-build which I 
used to build the previous version of maxima and I experienced no problems.

I've been in the habit of downloading the entire repository every time I 
want to upgrade Maxima, but this time, since I wanted to learn a little 
about git, I did the following in my cloned repository:

git checkout master
git branch -d pfb-build
git pull, which brought about 20 updates into the master branch
git branch pfb-build
git checkout pfb-build

This all seemed to work perfectly so I went through the build process;
bootstrap
configure --prefix=$HOME/maxima-test --enable-sbcl 
--with-sbcl=/usr/local/bin/sbcl
make
make check
make install

The make check step did not find any errors.
The error showed up when I ran the testsuite from within wxMaxima.
I just ran the testsuite from within xmaxima and got no errors.
I just ran the testsuite from within wxMaxima and it got the same error, 
so the problem is not Maxima's,but wxMaxima's. I didn't think to do that 
earlier.

The version of wxMaxima is wxMaxima 13.04.1.

Respectfully,

Paul Bowyer