After a fresh 2.9 build on
Dual-Core AMD Opteron(tm) Processor 2220
--testall just produxed this:
The following tests failed:
sage -t devel/sage-main/sage/calculus/calculus.py
Total time for all tests: 1424.9 seconds
Please see /home/jec/sage-2.9/tmp/test.log for the complete log from this test.
sage -t devel/sage-main/sage/calculus/calculus.py
**********************************************************************
File "calculus.py", line 2460:
sage: v.find_root(0, 0.002)
Expected:
0.0015403270679114178
Got:
0.0015403270679114176
**********************************************************************
File "calculus.py", line 2473:
sage: a.find_root(0,0.002)
Expected:
0.00041105140493493411
Got:
0.00041105140493493417
**********************************************************************
1 items had failures:
2 of 16 in __main__.example_50
***Test Failed*** 2 failures.
For whitespace errors, see the file .doctest_calculus.py
John
On 17/12/2007, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 17, 12:42 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> > On Dec 16, 2007 11:19 PM, mabshoff
> >
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Hello,
> >
> > > I ran sage "-testall -long" and sage "-testall -optional" on the 2.9
> > > release on sage.math. While -long passed with flying colors, -optional
> > > had some failures in tut.tex since I didn't install some optional GAP
> > > database. But there are also some problems with maxima, which might
> >
> > Maybe
> > database_gap-4.4.10
> > (There is also a newer version of this BTW.)
>
> Ok, I will install that db next time I test. At least the first two
> failure were related to some printing changes in 2.9:
>
> File "tut.py", line 3390:
> : G
> Expected:
> Group([ (1,2,3)(4,5), (3,4) ])
> Got:
> Group( [ (1,2,3)(4,5), (3,4) ] )
> **********************************************************************
> File "tut.py", line 3392:
> : G.Center()
> Expected:
> Group(())
> Got:
> Group( () )
>
> Those are easy enough to fix.
>
> > > just be fallout from the GAP failure. I will investigate, but it seems
> >
> > I don't think we have (at this point) any functions which mix maxima
> > and GAP code.
> > (I wish there were and would be happy to be corrected!)
>
> Nope, I looked and the maxima failures were all in plotting code, most
> likely related to the fact that I did run the test of an ssh connect
> without exporting X over ssh at the same time.
>
> > I did a sage -upgrade to 2.9 and had no serious problems but just notices
> > that
> > the startup banner is missing "2.9". Is that just me?
>
> I think William reported something similar. To fix it see the faq,
> specifically:
>
> # QUESTION: Upgrading Sage went fine, but now the banner still shows
> the old version. How can I fix this?
> # ANSWER: Try doing sage: hg_scripts.merge() followed by sage:
> hg_scripts.commit().
>
> > [EMAIL PROTECTED]:~/wdj/sagefiles/sage-2.9.alpha5$ ./sage
> > ----------------------------------------------------------------------
> > | SAGE Version rc4, Release Date: 2007-12-16 |
> > | Type notebook() for the GUI, and license() for information. |
> > ----------------------------------------------------------------------
> >
> > sage: version()
> > 'SAGE Version 2.9, Release Date: 2007-12-16'
> >
> > > that we are in reasonably good shape [William had feared that loads of
> > > things would go *boom*].
> >
> > > Cheers,
> >
> > > Michael
>
> Cheers,
>
> Michael
> >
>
--
John Cremona
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
