Built fine on OS X 32-bit intel, but there were some doctest failures,
which maybe you already know about:
sage -t -long "devel/sage/sage/combinat/words/words.py"
sage -t -long "devel/sage/sage/interfaces/psage.py"
sage -t -long "devel/sage/sage/schemes/elliptic_curves/monsky_washnitzer.py"
Total time for all tests: 7521.4 seconds
sage -t -long "devel/sage/sage/interfaces/psage.py"
**********************************************************************
File "/Users/was/build/sage-3.4.1.rc1/devel/sage/sage/interfaces/psage.py",
line 35:
sage: print "ignore this"; w # random output
Exception raised:
Traceback (most recent call last):
File "/Users/was/build/sage-3.4.1.rc1/local/bin/ncadoctest.py",
line 1231, in run_one_test
self.run_one_example(test, example, filename, compileflags)
File "/Users/was/build/sage-3.4.1.rc1/local/bin/sagedoctest.py",
line 38, in run_one_example
OrigDocTestRunner.run_one_example(self, test, example,
filename, compileflags)
File "/Users/was/build/sage-3.4.1.rc1/local/bin/ncadoctest.py",
line 1172, in run_one_example
compileflags, 1) in test.globs
File "<doctest __main__.example_0[5]>", line 1, in <module>
print "ignore this"; w # random output###line 35:
sage: print "ignore this"; w # random output
File "/Users/was/build/sage-3.4.1.rc1/local/lib/python2.5/site-packages/sage/interfaces/expect.py",
line 1514, in __repr__
s = s.replace(self._name, self.__dict__['__custom_name'])
KeyError: '__custom_name'
****************************************
sage -t -long "devel/sage/sage/schemes/elliptic_curves/monsky_washnitzer.py"
**********************************************************************
File "/Users/was/build/sage-3.4.1.rc1/devel/sage/sage/schemes/elliptic_curves/monsky_washnitzer.py",
line 1562:
sage: B.det() # long time
Expected:
11 + 484*t^2 + 451*t^3 + O(t^4)
Got:
245 + 240*t + 724*t^2 + 808*t^3 + O(t^4)
**********************************************************************
1 items had failures:
1 of 70 in __main__.example_32
***Test Failed*** 1 failures.
By the way, the notebook is *completely broken* in 3.4.1.rc1. The
one-line patch at
http://trac.sagemath.org/sage_trac/ticket/5703
fixes the problem. I hope somebody referees it!
William
>
> sage -t -long "devel/sage/sage/schemes/elliptic_curves/monsky_washnitzer.py"
> **********************************************************************
> File "/Users/was/build/sage-3.4.1.rc1/devel/sage/sage/schemes/elliptic_curves/monsky_washnitzer.py",
> line 1562:
> sage: B.det() # long time
> Expected:
> 11 + 484*t^2 + 451*t^3 + O(t^4)
> Got:
> 245 + 240*t + 724*t^2 + 808*t^3 + O(t^4)
> **********************************************************************
> 1 items had failures:
> 1 of 70 in __main__.example_32
> ***Test Failed*** 1 failures.
>
I confirm this. Also happening on Fedora 9, 32 bit.
Jaap
> here goes 3.4.1.rc1. This is actually a release that will build on OSX
> unlike 3.4.1.rc0.
[snip]
> You can upgrade to 3.4.1.rc1 by running
>
> ./sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/sage-3.4.1.rc1/
>
> Sources as well as a sage.math binary can be found in
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/
Built from scratch on Mac OS X, 10.5.6 (32-bit build on Dual Quad
Xeon) w/o problems.
Testing showed only one, previously-reported, failure:
sage -t -long "devel/sage/sage/combinat/words/words.py"
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
Experience is what you get
when you don't get what you want.
--------
On Apr 7, 2009, at 17:40 , mabshoff wrote:
> On Apr 7, 3:27 pm, "Justin C. Walker" <jus...@mac.com> wrote:
>> On Apr 6, 2009, at 14:42 , mabshoff wrote:
>>> here goes 3.4.1.rc1. This is actually a release that will build on
>>> OSX
>>> unlike 3.4.1.rc0.
>> [snip]
>>> You can upgrade to 3.4.1.rc1 by running
>>
>>> ./sage -upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/sa
>>> ...
>>
>>> Sources as well as a sage.math binary can be found in
>>
>>> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.1/
>>
>> Built from scratch on Mac OS X, 10.5.6 (32-bit build on Dual Quad
>> Xeon) w/o problems.
>>
>> Testing showed only one, previously-reported, failure:
>>
>> sage -t -long "devel/sage/sage/combinat/words/wo rds.py"
>>
>> Justin
>
> That one is fixed. I am surprised you did not get the mosky failure,
> but I suspected if you did a -ba you would hit it.
Ha! I just (well, a while back) did './sage -ba' and then
./sage -t devel/sage/sage/schemes/elliptic_curves/
monsky_washnitzer.py
All tests passed! :-}
Go figure. Maybe it's that metal plate in my head.
J
--
Justin C. Walker
Curmudgeon-at-large
Director
Institute for the Absorption of Federal Funds
----
186,000 Miles per Second
Not just a good idea:
it's the law!
----
I built 3.4.1.rc1 on my Asus EEE PC 1000H (Intel Atom). The previous
issue with gmp-mpir not compiling has been fixed (thanks to Bill Hart
and others) but I get a doctest failure on calculus.py. The first time
I ran sage -testall I saw this:
sage -t "devel/sage/sage/calculus/calculus.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
*** *** Error: TIMED OUT! *** ***
*** *** Error: TIMED OUT! *** ***
[361.7 s]
When I tried to run sage -t calculus.py independently I got 700k of output:
http://carlo-hamalainen.net/sagetmp/calc.txt.gz
--
Carlo Hamalainen
http://carlo-hamalainen.net
IMHO, the file calculus.py is too big. It has more than 10,000 lines
of codes. While adding new doc-tests to it, I had to wait
several minutes for each doc-test.
I will be good to have separate files for some of the long class
definitions inside it. These classes can then be imported into
calculus.
Cheers,
Golam
It may be a waste of time to refactor calculus.py right now, since we
will be moving to a completely different symbolic calculus
implementation in the near future. (That's the pynac stuff.)
William