I only had two test failures after a successful build:
sage -t devel/sage/sage/misc/prandom.py
sage -t devel/sage/sage/misc/inline_fortran.py
In detail:
sage -t devel/sage/sage/misc/prandom.py
**********************************************************************
File "/home/jec/sage-3.0.alpha1/tmp/prandom.py", line 285:
sage: [vonmisesvariate(1.0r, 3.0r) for i in range(1, 5)]
Expected:
[0.89832863935542584, 0.67180300070412846, 2.0308777524813397,
1.7143252537251459]
Got:
[0.89832863935542584, 0.67180300070412846, 2.0308777524813397,
1.7143252537251454]
**********************************************************************
and
sage -t devel/sage/sage/misc/inline_fortran.py
**********************************************************************
File "/home/jec/sage-3.0.alpha1/tmp/inline_fortran.py", line 28:
sage: test_fortran(s) # -- requires fortran
Expected nothing
Got:
Found executable /home/jec/sage-3.0.alpha1/local/bin/sage-g77_shared
Found executable /home/jec/sage-3.0.alpha1/local/bin/sage_fortran
Found executable /usr/bin/ld
Found executable /usr/bin/ar
Found executable /usr/bin/ranlib
<BLANKLINE>
**********************************************************************
File "/home/jec/sage-3.0.alpha1/tmp/inline_fortran.py", line 31:
sage: fib(n,int(10)) # -- requires fortran
Exception raised:
Traceback (most recent call last):
File "/home/jec/sage-3.0.alpha1/local/lib/python2.5/doctest.py",
line 1212, in __run
compileflags, 1) in test.globs
File "<doctest __main__.example_0[7]>", line 1, in <module>
fib(n,int(Integer(10))) # -- requires fortran###line 31:
sage: fib(n,int(10)) # -- requires fortran
NameError: name 'fib' is not defined
**********************************************************************
File "/home/jec/sage-3.0.alpha1/tmp/inline_fortran.py", line 32:
sage: n # -- requires fortran
Expected:
array([ 0., 1., 1., 2., 3., 5., 8., 13., 21., 34.])
Got:
array([ 0., 1., 2., 3., 4., 5., 6., 7., 8., 9.])
**********************************************************************
On 05/04/2008, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 5, 2:35 am, mabshoff <[EMAIL PROTECTED]
>
> dortmund.de> wrote:
> > Hello folks,
> >
> > here is Sage 3.0.alpha1. The bad news upfront: The gcc 4.3
> > compiler support didn't make it since the updated Singular
> > SPKG is delayed due to some bugs. Martin Albrecht is working
> > on it, so hopefully it will be in alpha2. We merged a massive
> > number of tickets hours before alpha1 mostly thanks to Mike
> > Hansen who did review a whole bunch of tickets. Other
> > interesting bits:
> >
> > * the modabvar rewrite has been merged thanks to much work
> > by William Stein, Craig Citro, Robert Bradshaw
> > * much work for PolyBoRi, libSingular and Magma by Martin
> > Albrecht
> > * LinBox has been updated to the final 1.1.5 release thanks
> > due to Clement Pernet
> > * Many fixes and speedups to Elliptic curves, discrete log
> > and various other bits by John Cremona
> > * Carl Witty's new new "randstate" framework
> > * A Tonelli-Shanks implementation by Steffan Reidt and
> > Robert Bradshaw
> > * Cython 0.9.6.13 has been merged thanks to Gary Furnish and
> > Robert Bradshaw. This was a requirement to merge Gary's fast
> > symbolics subsystem
> >
> > Sorry for anybody I did forget. It has been a wild merge session
> > for the last twelve+ hours. What is most important:
> >
> > Overall weighted coverage score: 50.0%
> > Total number of functions: 19290
> >
> > w00t! Sources and binaries in the usual space. This build will
> > be the basis of Bug Day 11 tomorrow.
> >
> > Sources:
> >
>
> > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage...
> >
> > Binary:
> >
> > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage...
>
> >
> > What is up next?
> >
> > * gcc 4.3 support
> > * More of OSX 10.5 64 bit support
> > * merges, merges, merges
> >
> > Cheers,
> >
> > Michael
>
>
>
> Ok, there is trouble in paradise:
>
> #2804: ssmod.py doctest failure - this is likely LinBox related. It
> happens only on occasion and I didn *never* hit in on 20+ full doctest
> runs on sage.math. Gary did hit it on his Dual QuadCore a couple
> times.
>
> #2802: inline_fortran.py doctest failure - we are unsure *what* caused
> it. It did pop up at some point and I didn't pay attention until a day
> later when I realized that it was reproducible. We suspect #2746 - any
> ideas Tim?
>
> Cheers,
>
> Michael
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
