#9460: Many Maxima-related doctest failures on sage.math
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.5
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by drkirkby):
I'm attaching a log of
$ make ptestlong
on sage.math. I did forget, and actually built this in $HOME, not on a
scratch disk. However, I did not use a script.
Ultimately there are 4 failures.
{{{
The following tests failed:
sage -t -long devel/sage/sage/interfaces/expect.py # 11 doctests
failed
sage -t -long devel/sage/sage/interfaces/r.py # 184 doctests
failed
sage -t -long devel/sage/sage/stats/r.py # 1 doctests failed
sage -t -long devel/sage/sage/tests/startup.py # 1 doctests
failed
----------------------------------------------------------------------
}}}
All Maxima tests appear to have passed as far as I can see.
One possibility for the changed behavior might be the changes to 'deps'.
This is now much better than it was before, with more accurate rules about
the order things are built. This could mean that the build order has
changed from previous versions of Sage and possibly libraries in Sage are
now used when before the system libraries might be used - or visa versa.
Another useful to track this might be to write a script that
* Build Sage with the old maxima. Run just the maxima test to reduce the
time.
* Build Sage with the old ECL. Run just the maxima test to reduce the
time.
* Build Sage with the old maxima and old ECL. Run just the maxima test to
reduce the time.
* Build Sage with the new Maxima and new ECL. Run just the maxima test to
reduce the time.
Repeat the above 10 times. Then look at the results, and see if failures
are correlated or not.
I see from his comment above William rolled back Maxima, and started a
build. That has now finished. All his Maxima tests pass, but he gets this
failure - which is new as far as I can see. I've just built Sage on
sage.math without this failure.
http://sage.math.washington.edu/home/wstein/build/sage-4.5.alphastein1/testlong.log
{{{
----------------------------------------------------------------------
The following tests failed:
sage -t -long
"devel/sage/sage/schemes/elliptic_curves/lseries_ell.py"
Total time for all tests: 8270.6 seconds
}}}
Why should changing Maxima make
{{{devel/sage/sage/schemes/elliptic_curves/lseries_ell.py}}} fail? I
suspect the real cause of these problems might not be Maxima at all. There
appears to be sporadic problems in this release of Sage (William for
example failed to get R to build on OS X, but that works for me).
This is a shame, as I know Robert has put a lot of effort into this
release. I was actually expecting it to be one of the more stable Sage
releases - which hopefully it will be, once the problem is resolved.
Is it possible GPLK is responsible for this? That is a new standard
package. I agree it seems unlikely, but I'm not convinced it is just a
Maxima issue. Most likely is a build issue, which makes me think 'deps'
might be the cause.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9460#comment:21>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
