Hi,
while Felix spends his summer trying to modify sage's architecture for a
better integration in distributions, I'm still playing with the little
problems.
My little script which makes sage think it compiled things while it
really gets the system packages gives the following results:
- it almost builds sage:
(1) something(what?!) comes and kills my libatlas.so.3gf link, which I
have to recreate by hand
(2) currently ecl+maxima from debian aren't used (hence I also use
sage's boehm-gc), I'll work on it next week
- documentation builds (#14626 got closed), which is a new achievement ;
- ptestlong doesn't find that many problems, but I'm wondering about
some of them ; comments are very welcome -- see the end of this mail.
Cheers,
Snark on #sagemath
PS:
# Two doctests fail because sage expects palp to break for large objects
# and debian's package doesn't!
# (sage: 7 vs debian:11)
sage -t --long devel/sage/sage/geometry/lattice_polytope.py
# A single failure:
# Failed example:
# r._expect.before
# Expected:
# 'abc;\r\n[1] '
# Got:
# 'abc <- 10 +15;\r\n__SAGE__R__PROMPT__> abc;\r\n[1] '
sage -t --long devel/sage/sage/interfaces/expect.py
# I need to investigate what is tested ; the two failures,
# line 177 and 185 are similar:
# Failed example:
# os.WIFEXITED(status) and os.WEXITSTATUS(status) != 0
# Expected:
# True
# Got:
# False
sage -t --long devel/sage/sage/misc/interpreter.py
# Warnings get us bitten:
# Failed example:
# sage_getdoc(g) == sage_getdoc(gcd)
# Expected:
# True
# Got:
# doctest:29: ImportWarning: Not importing directory
'/home/jpuydt/sage-5.11.beta3.debian/devel/sage/doc/en': missing __init__.py
# doctest:34: ImportWarning: Not importing directory
'/home/jpuydt/sage-5.11.beta3.debian/devel/sage/doc/en': missing __init__.py
# True
sage -t --long devel/sage/sage/structure/element.pyx
# What is it trying to test indirectly!?
# Failed example:
# sympy.nan == NaN # indirect doctest
# Expected:
# True
# Got:
# False
sage -t --long devel/sage/sage/symbolic/constants.py
# I need to look into what is getting tested:
# Failed example:
# DC.test_safe_directory(d)
# Expected:
# Traceback (most recent call last):
# ...
# RuntimeError: refusing to run doctests...
# Got:
# <BLANKLINE>
sage -t --long devel/sage/sage/doctest/control.py
# Two cases of expecting "RuntimeError: refusing to run doctests..." and
getting
# a <BLANKLINE> -- why should it be refused!?
# and a single trivial problem:
# Failed example:
# open(os.path.join(SAGE_LOCAL, "bin", "ipython")).readline()
# Expected:
# '#!/usr/bin/env python\n'
# Got:
# '#! /usr/bin/python\n'
sage -t --long devel/sage/sage/tests/cmdline.py
# A single pari crash (when will 2.6 get out!?):
# Failed example:
# L.zeros(10)
# Expected:
# *** Warning: new stack size = ...
# [0.000000000, 0.000000000, 2.87609907, 4.41689608, 5.79340263,
# 6.98596665, 7.47490750, 8.63320525, 9.63307880, 10.3514333]
# Got:
# *** Warning: new stack size = 1098912 (1.048 Mbytes).
# *** Error in the PARI system. End of program.
# []
sage -t --long devel/sage/doc/en/bordeaux_2008/elliptic_curves.rst
# Three instances of pari needing a new stack size and crashing
# (when will 2.6 get out!?)
sage -t --long devel/sage/sage/schemes/elliptic_curves/lseries_ell.py
# Two cases of asking a function's source and getting a slightly different
# output, and two cases of asking R's version and not getting the same...
#
sage -t --long devel/sage/sage/interfaces/r.py
# A few failing tests because matplotlib doesn't find X ; with X one of the
# tests fails because there's a warning:
# Fontconfig warning: "/etc/fonts/conf.d/25-wqy-zenhei.conf", line 11:
Having multiple values in <test> isn't supported and may not work as
expected
# but I think it's a debian bug not a serious problem
sage -t --long devel/sage/sage/gsl/probability_distribution.pyx
# This test might be a joke:
# Failed example:
# 'numpy' in sys.modules
# Expected:
# False
# Got:
# True
sage -t --long devel/sage/sage/tests/startup.py
# Would debian miss some patch for some syntactic sugar?
# Failed example:
# shell.run_cell('%time 594.factor()')
# Expected:
# CPU times: user ...
# Wall time: ...
# 2 * 3^3 * 11
# Got:
# File "<timed exec>", line 1
# 594.factor()
# ^
# SyntaxError: invalid syntax
# <BLANKLINE>
sage -t --long devel/sage/sage/misc/sage_extension.py
# The two failures are part due to different paths
# and a little differing output, so shouldn't hurt:
# Failed example:
# print sage0("d.listing(1)")
# Expected:
# 2... x = a + b
# --> ... y = a * b
# ... return x, y, x<y, x>y # < to ensure HTML is
properly escaped
# <hr>> <a href="/src/interacts/debugger.py"
target="_new">devel/sage/sage/interacts/debugger.py</a>
# Got:
# 24 x = a + b
# --> 25 y = a * b
# 26 return x, y, x<y, x>y # < to ensure HTML is
properly escaped
# <hr>>
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/sage/interacts/debugger.py
# Failed example:
# print sage0("d.listing(1)")
# Expected:
# 4... else:
# --> ... test_function2(m, n)
# ...
# <hr>> <a href="/src/interacts/debugger.py"
target="_new">devel/sage/sage/interacts/debugger.py</a>
# Got:
# 40 else:
# --> 41 return test_function2(m, n)
# 42
# <hr>>
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/sage/interacts/debugger.py
sage -t --long devel/sage/sage/interacts/debugger.py
# display difference
sage -t --long devel/sage/sage/calculus/test_sympy.py
# the GLPK version embedded in the expected result
sage -t --long devel/sage/sage/numerical/mip.pyx
# debian is missing the testjava shell script
sage -t --long devel/sage/sage/interfaces/jmoldata.py
# I wonder what is being tested here:
# Failed example:
# for i in frames:
# filename, lineno, funcname, linelist, indx =
inspect.getframeinfo(i)
# for nm in allowed:
# if nm in filename:
# break
# else:
# print filename
# Expected nothing
# Got:
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/jinja2/_compat.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/jinja2/utils.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/jinja2/nodes.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/jinja2/environment.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/jinja2/__init__.py
#
/home/jpuydt/sage-5.11.beta3.debian/devel/sagenb/sagenb/notebook/template.py
# /home/jpuydt/sage-5.11.beta3.debian/devel/sagenb/sagenb/notebook/css.py
#
/home/jpuydt/sage-5.11.beta3.debian/devel/sagenb/sagenb/notebook/notebook.py
#
/home/jpuydt/sage-5.11.beta3.debian/devel/sagenb/sagenb/notebook/notebook_object.py
# /home/jpuydt/sage-5.11.beta3.debian/devel/sagenb/sagenb/notebook/all.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/sage/server/notebook/all.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/sage/server/all.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/sage/all.py
#
/home/jpuydt/sage-5.11.beta3.debian/local/local/lib/python2.7/dist-packages/sage/all_cmdline.py
sage -t --long devel/sage/sage/all.py
# Two cases of pari crashing because it had to resize it's stack (when
# will 2.6 get out!?), and a case of " TypeError: unable to convert x (=)
# to an integer" on which I have no clue
sage -t --long devel/sage/sage/lfunctions/lcalc.py
# One failure, which is debian bug #709073
sage -t --long devel/sage/sage/interfaces/genus2reduction.py
# Two differing output... which is strange since we have the same version
# in debian and sage... I need to investigate.
sage -t --long devel/sage/sage/libs/fplll/fplll.pyx
# Pari crashes (when will 2.6 get out!?)
sage -t --long devel/sage/sage/libs/pari/gen.pyx
# A lot of problems due to needing an X display, and two cases where I
# think what's being tested should perhaps be detected differently:
#Failed example:
# len((q1).matplotlib().axes[0].legend().texts) # used to raise
AttributeError
# Expected:
# 1
# Got:
# 2
# Failed example:
# len(p1.matplotlib().axes[0].legend().texts)
# Expected:
# 1
# Got:
3
sage -t --long devel/sage/sage/plot/plot.py
# Two cases of the above "unable to convert x (=) to an integer", which
I don't
# know about and another case of debian perhaps having something
compiled with
# some parameter and debian compiling with a slightly bigger one:
# Failed example:
# E.saturation([2*P]) ## needs higher precision
# Expected:
# After 10 attempts at enlargement, giving up!
# ...
#
([(1755450733726721618440965414535034458701302721700399/970334851896750960577261378321772998240802013604
:
-59636173615502879504846810677646864329901430096139563516090202443694810309127/955833935771565601591243078845907133814963790187832340692216425242529192
: 1)], 2, 113.302910926080)
# Got:
#
([(697059763916839811078337858798347162470013766225553/125882473941508715401055010125120306742453617664
:
17964093978634735025234271759384575412627262961292171402552454280120845611703/44663001336009603558781167435086158167457788739030704541177457005068288
: 1)], 2, 113.302910926080)
sage -t --long devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
