Hi,

builds fine on MacIntel (32bit) OS X 10.4, but there are four (long)
doctest failures:
----------------------------------------------------------------------
The following tests failed:


        sage -t -long "devel/sage/sage/misc/abstract_method.py"
        sage -t -long "devel/sage/sage/misc/lazy_attribute.py"
        sage -t -long "devel/sage/sage/parallel/decorate.py"
        sage -t -long "devel/sage/sage/symbolic/expression.pyx"
Total time for all tests: 20130.6 seconds

The first two ones and the last one have been reported earlier in this
thread, the last one already for 4.1.1.alpha0 IIRC.
I have seen myself the third one, "decorate.py" failure before, it
always hits me. On my system, it even occurs for the official Sage 4.1
release. Sorry I didn't report it before, I didn't believe I was the
only one to see it, it is a Python 2.6 issue:

sage -t -long "devel/sage/sage/parallel/decorate.py"
**********************************************************************
File "/Users/Shared/sage/sage-4.1.1.alpha1/devel/sage/sage/parallel/
decorate.py", line 64:
    sage: @parallel()
    def f(N): return N**Integer(2)
Expected nothing
Got:
    doctest:49: DeprecationWarning: os.popen2 is deprecated.  Use the
subprocess module.
**********************************************************************
1 items had failures:
   1 of   6 in __main__.example_3
***Test Failed*** 1 failures.
For whitespace errors, see the file /Users/Shared/sage/
sage-4.1.1.alpha1/tmp/.doctest_decorate.py
         [7.1 s]

A quick glance at "decorate.py" revealed nothing immediate. Is this
failure due to some OS X 10.4 peculiarities of the pyprocessing
module?

Cheers,
Georg
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to