Re: [sage-release] square root very strange in 8.5.beta3

[Erik Bray]

On Wed, Nov 14, 2018 at 10:32 AM Bruno Grenet  wrote:
>
> As far as I can tell, this behavior is not new. The (default) choice
> made for the square root of an integer is to return an exact answer
> rather than an approximation. Thus sqrt(9) = 3, sqrt(10) = sqrt(10) and
> sqrt(12) = 2*sqrt(3). On the other hand, a floating point number is
> viewed as an approximation of a real number so the value returned by
> sqrt is then an approximation of the square root.
>
> Note that the default behavior for integers can be changed using
> optional parameters:
>
> sage: sqrt(10, prec=100)
> 3.1622776601683793319988935444
> sage: sqrt(10, prec=100, all=True)
> [3.1622776601683793319988935444, -3.1622776601683793319988935444]

I agree that this behavior makes sense.

However, one thing I do find surprising about the global sqrt
function, which is different from some other global functions (I
think, needlessly) is that it does not work as a symbolic function.
By contrast, the exp function also exhibits the above behavior, in
that it will reduce to an exact (integer) value where possible:

sage: exp(0)
1
sage: exp(2)
e^2

However, if I really wanted to have `exp(0)` as a symbolic expression
I can still do:

sage: exp(0, hold=True)
e^0

This *ought* to work the same way for sqrt or any other function IMO,
but the sqrt global does not accept the hold argument by default:

sage: sqrt(4, hold=True)
---
TypeError Traceback (most recent call last)
 in ()
> 1 sqrt(Integer(4), hold=True)

/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/functions/other.pyc
in sqrt(x, *args, **kwds)
884 except (AttributeError, TypeError):
885 pass
--> 886 return _do_sqrt(x, *args, **kwds)
887
888 # register sqrt in pynac symbol_table for conversion back from
other systems

TypeError: _do_sqrt() got an unexpected keyword argument 'hold'


Looking at the docstring for sqrt, this behavior is actually
documented, and it works if you explicitly coerce the argument to the
symbolic ring:

sage: sqrt(SR(4), hold=True)
sqrt(4)

But again, that seems to be inconsistent, and also an unnecessary
limitation.  If hold=True is passed in that would imply that you want
a symbolic result, and that should "just work" so long as the argument
can be coerced to a symbolic expression.

Unless there's some subtle reason I'm wrong here, I'll open a ticket...

Best,
E


> Le 14/11/2018 à 09:20, Henri Girard a écrit :
> > HI,
> >
> > I am calculating a square root sqrt(9)=3
> >
> > But at 10 and over I got this answer sqrt(10)= sqrt(10) except
> > sqrt(16)=4 when it's a right square
> >
> > but sqrt(10.0)=3.16... Is it a normal answer ?
> >
> > sqrt(16)=4 works
> >
> > Any explaination ?
> >
> > Regards
> >
> > Henri
> >
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] square root very strange in 8.5.beta3

[Erik Bray]

On Thu, Nov 15, 2018 at 8:39 AM Emmanuel Charpentier
 wrote:
>
>
>
> Le mercredi 14 novembre 2018 12:29:36 UTC+1, Erik Bray a écrit :
>
>>
>> However, one thing I do find surprising about the global sqrt
>> function, which is different from some other global functions (I
>> think, needlessly) is that it does not work as a symbolic function.
>> By contrast, the exp function also exhibits the above behavior, in
>> that it will reduce to an exact (integer) value where possible:
>
>
> This is more general than that : the support for "hold" argument is 
> inconstant. Compare :
> sage: sin(x).integrate(x,hold=True)
> integrate(sin(x), x)
> sage: sin(x).diff(x,hold=True)
> ---
> TypeError Traceback (most recent call last)
>  in ()
> > 1 sin(x).diff(x,hold=True)
>
> TypeError: derivative() got an unexpected keyword argument 'hold'
>
> Sage has some analogous inconsistencies :
>
> sage: f(x)=piecewise([((-oo,-1),x^3),([-1,1],x),((1,oo),x^2)],var=x); f
> x |--> piecewise(x|-->x^3 on (-oo, -1), x|-->x on [-1, 1], x|-->x^2 on (1, 
> +oo); x)
> sage: f(x).integral(x)
> piecewise(x|-->1/4*x^4 - 1/4 on (-oo, -1), x|-->1/2*x^2 - 1/2 on [-1, 1], 
> x|-->1/3*x^3 - 1/3 on (1, +oo); x)
> sage: f(x).integrate(x)
> ---
> TypeError Traceback (most recent call last)
>  in ()
> > 1 f(x).integrate(x)
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/symbolic/expression.pyx
>  in sage.symbolic.expression.Expression.integral 
> (build/cythonized/sage/symbolic/expression.cpp:69368)()
>   12399 R = ring.SR
>   12400 return R(integral(f, v, a, b, **kwds))
> > 12401 return integral(self, *args, **kwds)
>   12402
>   12403 integrate = integral
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/symbolic/integration/integral.pyc
>  in integrate(expression, v, a, b, algorithm, hold)
> 816 return integrator(expression, v, a, b)
> 817 if a is None:
> --> 818 return indefinite_integral(expression, v, hold=hold)
> 819 else:
> 820 return definite_integral(expression, v, a, b, hold=hold)
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/symbolic/function.pyx
>  in sage.symbolic.function.BuiltinFunction.__call__ 
> (build/cythonized/sage/symbolic/function.cpp:11950)()
> 996 res = self._evalf_try_(*args)
> 997 if res is None:
> --> 998 res = super(BuiltinFunction, self).__call__(
> 999 *args, coerce=coerce, hold=hold)
>1000
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/symbolic/function.pyx
>  in sage.symbolic.function.Function.__call__ 
> (build/cythonized/sage/symbolic/function.cpp:6977)()
> 490 (args[0])._gobj, hold)
> 491 elif self._nargs == 2:
> --> 492 res = g_function_eval2(self._serial, 
> (args[0])._gobj,
> 493 (args[1])._gobj, hold)
> 494 elif self._nargs == 3:
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/symbolic/integration/integral.pyc
>  in _eval_(self, f, x)
>  88 for integrator in self.integrators:
>  89 try:
> ---> 90 return integrator(f, x)
>  91 except NotImplementedError:
>  92 pass
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/symbolic/integration/external.pyc
>  in maxima_integrator(expression, v, a, b)
>  30 expression = SR(expression)
>  31 if a is None:
> ---> 32 result = maxima.sr_integral(expression,v)
>  33 else:
>  34 result = maxima.sr_integral(expression, v, a, b)
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.pyc
>  in sr_integral(self, *args)
> 807 """
> 808 try:
> --> 809 return 
> max_to_sr(maxima_eval(([max_integrate],[sr_to_max(SR(a)) for a in args])))
> 810 except RuntimeError as error:
> 811 s = str(error)
>
> /usr/local/sage-8/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.pyc
>  in max_to_sr(expr)
>1684 op_max=caar(expr)
>1685 if op_max in special_max_to_sage:
> -> 1686 return special_max_to_sage[op_max](expr)
>1687 if not(op_max in max_op_dict):
>1688  

Re: [sage-release] Sage 8.5.beta4 released

[Erik Bray]

I might have missed it, but have you ever mentioned if there is a
target release date and/or cutoff date for non-critical issues for
this version?
On Sun, Nov 18, 2018 at 9:30 PM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> f894105d0d (tag: 8.5.beta4, trac/develop) Updated SageMath version to 
> 8.5.beta4
> 0d328f Trac #26698: py3: fix some doctests in eta products
> b3be1d58a9 Trac #26691: fixing some invalid escape sequences
> bdf0e6a8f4 Trac #26677: rational_points for some elliptic curves fails
> 835640b08a Trac #26690: some work on cluster mutation
> 28d042668f Trac #26689: py3: fix doctests in misc_c.pyx
> abc48c6b9d Trac #26703: py3: action.pyx and spanning_tree.pyx
> aa0f6c26f2 Trac #26701: Simplifications in the computation of the inverse of 
> a transition map
> 227b82c6fc Trac #26700: minor changes in doctest control
> 144ee5b03a Trac #26694: remove a deprecated special function
> d35c467afc Trac #26693: remove one deprecated function in octave interface
> d0dcdd26a6 Trac #16931: Elliptic curve point counting over F_q using PARI
> 7f1d54f493 Trac #26696: py3: fixing Kleber trees
> 0142c20a59 Trac #26685: fix a bad import in abstract trees
> 025e9f3794 Trac #26695: pyflakes cleanup for Coxeter groups as matrix groups
> d29ab29faa Trac #26692: py3: fix Tate algebras
> b674a8c73e Trac #26688: py3: some fixes in quaternion algebras
> 4b97f54eb9 Trac #26683: py3: various fixes in combinat
> 1d7c682c58 Trac #26659: py3: Fix some doctests errors in sets module for 
> python3
> 8e3e82c990 Trac #26550: Upgrade to SymPy 1.3
> c711b44106 Trac #26686: sagenb docs fail to build
> 3c78d880eb Trac #26558: doc-pdf fails due to conflict with new babel.sty
> aedea2f258 Trac #26684: py3: fixing round in random graph generator
> d701ae4bbe Trac #26664: py3: fix tensor operations for Klyachko bundles
> c8aff975ef Trac #25885: Fixes for outdated Macaulay2 interface
> 02017bf7c1 Trac #26662: pep cleanup of Weierstrass covering
> d19f89a877 Trac #24065: p-adic polynomial - factorization with pari fails.
> 337e4da01b Trac #26671: py3: fix doctests in latin squares
> 370ae21eec Trac #26670: py3: cleanup of toy d basis
> 2ae1e80fb1 Trac #26669: Error when factoring constant p-adic polynomials
> 657362ee1e Trac #26172: Plot standard tableau with descents
> dee1f88fef Trac #26674: py3: fix doctests in weak dict
> 36f9a00e56 Trac #26673: py3: make some doctests of modular symbols more robust
> 92759f1f2f Trac #26672: clean generic_graph.py (part 10) - degree
> 91456e6c70 Trac #2: clean generic_graph.py (part 9) - edge and vertex 
> handlers
> 8bcd3090b5 Trac #26665: python3: 'filter' object is not subscriptable in 
> libs/gap/util.pyx
> 8dafc4e9d3 (tag: 8.5.beta3) Updated SageMath version to 8.5.beta3
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.5.beta4 released

[Erik Bray]

Thanks! Sounds good.  Sounds like we probably won't have GAP 4.10 in
time for that then, most likely... :(

Perhaps we can make a 8.6 relatively quicker after...  I'll do what I
can in the meantime, but I have my doubts.

On Tue, Nov 20, 2018 at 6:41 PM Volker Braun  wrote:
>
> December 1st is feature freeze
> Jan 1st ist release target
>
>
> On Tuesday, November 20, 2018 at 5:55:56 PM UTC+1, Erik Bray wrote:
>>
>> I might have missed it, but have you ever mentioned if there is a
>> target release date and/or cutoff date for non-critical issues for
>> this version?
>> On Sun, Nov 18, 2018 at 9:30 PM Volker Braun  wrote:
>> >
>> > As always, you can get the latest beta version from the "develop" git 
>> > branch. Alternatively, the self-contained source tarball is at 
>> > http://www.sagemath.org/download-latest.html
>> >
>> > f894105d0d (tag: 8.5.beta4, trac/develop) Updated SageMath version to 
>> > 8.5.beta4
>> > 0d328f Trac #26698: py3: fix some doctests in eta products
>> > b3be1d58a9 Trac #26691: fixing some invalid escape sequences
>> > bdf0e6a8f4 Trac #26677: rational_points for some elliptic curves fails
>> > 835640b08a Trac #26690: some work on cluster mutation
>> > 28d042668f Trac #26689: py3: fix doctests in misc_c.pyx
>> > abc48c6b9d Trac #26703: py3: action.pyx and spanning_tree.pyx
>> > aa0f6c26f2 Trac #26701: Simplifications in the computation of the inverse 
>> > of a transition map
>> > 227b82c6fc Trac #26700: minor changes in doctest control
>> > 144ee5b03a Trac #26694: remove a deprecated special function
>> > d35c467afc Trac #26693: remove one deprecated function in octave interface
>> > d0dcdd26a6 Trac #16931: Elliptic curve point counting over F_q using PARI
>> > 7f1d54f493 Trac #26696: py3: fixing Kleber trees
>> > 0142c20a59 Trac #26685: fix a bad import in abstract trees
>> > 025e9f3794 Trac #26695: pyflakes cleanup for Coxeter groups as matrix 
>> > groups
>> > d29ab29faa Trac #26692: py3: fix Tate algebras
>> > b674a8c73e Trac #26688: py3: some fixes in quaternion algebras
>> > 4b97f54eb9 Trac #26683: py3: various fixes in combinat
>> > 1d7c682c58 Trac #26659: py3: Fix some doctests errors in sets module for 
>> > python3
>> > 8e3e82c990 Trac #26550: Upgrade to SymPy 1.3
>> > c711b44106 Trac #26686: sagenb docs fail to build
>> > 3c78d880eb Trac #26558: doc-pdf fails due to conflict with new babel.sty
>> > aedea2f258 Trac #26684: py3: fixing round in random graph generator
>> > d701ae4bbe Trac #26664: py3: fix tensor operations for Klyachko bundles
>> > c8aff975ef Trac #25885: Fixes for outdated Macaulay2 interface
>> > 02017bf7c1 Trac #26662: pep cleanup of Weierstrass covering
>> > d19f89a877 Trac #24065: p-adic polynomial - factorization with pari fails.
>> > 337e4da01b Trac #26671: py3: fix doctests in latin squares
>> > 370ae21eec Trac #26670: py3: cleanup of toy d basis
>> > 2ae1e80fb1 Trac #26669: Error when factoring constant p-adic polynomials
>> > 657362ee1e Trac #26172: Plot standard tableau with descents
>> > dee1f88fef Trac #26674: py3: fix doctests in weak dict
>> > 36f9a00e56 Trac #26673: py3: make some doctests of modular symbols more 
>> > robust
>> > 92759f1f2f Trac #26672: clean generic_graph.py (part 10) - degree
>> > 91456e6c70 Trac #2: clean generic_graph.py (part 9) - edge and vertex 
>> > handlers
>> > 8bcd3090b5 Trac #26665: python3: 'filter' object is not subscriptable in 
>> > libs/gap/util.pyx
>> > 8dafc4e9d3 (tag: 8.5.beta3) Updated SageMath version to 8.5.beta3
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "sage-release" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an 
>> > email to sage-release...@googlegroups.com.
>> > To post to this group, send email to sage-r...@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/sage-release.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.5.beta5 released

[Erik Bray]

On Fri, Dec 2, 2016 at 2:06 AM, François Bissey
 wrote:
> Can please people stop using files in SAGE_SRC at runtime and people
> stop reviewing such things positively unless there is absolutely no
> choices.
>
> In sage/plot/plot3d/base.pyx we have line 410 and after:
> from sage.env import SAGE_SRC
> filename = os.path.join(SAGE_SRC, 'sage',
> 'plot', 'plot3d', 'threejs_template.html')
> f = open(filename, 'r')
> html = f.read()
> f.close()
>
> If you really need this at run time, ship it and access
> it relative to SAGE_LIB instead of SAGE_SRC. Thank you #12402.

I agree. Runtime dependencies on SAGE_SRC have really been a pain in
trying to package Sage.  It's basically impossible to package without
the source code and that's not really how to do this...

> On 02/12/16 12:15, Volker Braun wrote:
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> 163489e Updated SageMath version to 7.5.beta5
>> d1d859d Trac #22000: The coding conventions for INPUT: blocks have periods
>> 0d7c45d Trac #21805: Use psutil instead of various hacks
>> 909d9e1 Trac #12402: Make a three.js backend for 3d plotting
>> df2adac Trac #8181: cannot convert residue field elements back to p-adic
>> ring
>> f5afa90 Trac #21979: Wrong conversion from algebraic to interval
>> 6d380f9 Trac #21947: Don't let "tightpage" in view cut tikz images
>> ee25e65 Trac #21647: Doctest continuation marker / combinat
>> 4baf341 Trac #20692: Add sage-apply-patches helper script for use in
>> spkg-install scripts
>> 5944641 Trac #21988: Implement epimorphisms from finitely presented group.
>> 21d920f Trac #21982: Py3: Unicode errors in docstrings
>> 2306db0 Trac #21895: Better metaclass inference in dynamic classes
>> 14b6fe7 Trac #21911: Docstring for IncidenceStructure.is_uniform has
>> issues
>> d7e2d06 Trac #21949: some various typos
>> 1490af2 Trac #21978: py3 richcmp in pyx files for finite rings
>> 94b5b1d Trac #21970: py3 richcmp in function fields (pyx)
>> 9acd3ad Trac #21967: little cleanup for universal cyclotomic field
>> 20ea82e Trac #21964: py3 richcmp in 2 pyx files (in structure and
>> symbolic folders)
>> 8cc8ff5 Trac #21491: IndexError in integral_points_count of Polyhedron
>> 056f5c6 Trac #21953: Chain complexes: implement shift (= translation =
>> suspension)
>> f022846 Trac #21929: Make "tightpage=True" the default behavior for view
>> 04deb1f Trac #21925: Remove some deprecated code
>> dc97fb2 Trac #21960: Get rid of six.itervalues in Cython
>> 0da1c25 Trac #21701: Compiling sagelib with clang on OS X (Sierra):
>> failure in cythonized sage/symbolic/expression.pyx
>> cbb59f1 Trac #21962: Don't import max from builtins
>> abd7ed7 Trac #21961: Get rid of six.moves.range in Cython files (step 4)
>> 2068019 Trac #21958: py3 richcmp in Laurent and power series (pyx files)
>> 113c7c2 Trac #21955: py3 get rid of cmp() in two pyx files in modular
>> folder
>> 68a5e5a Trac #21938: Problem in the documentation of block design
>> 0cd8bb6 Trac #21930: Add rank for hypergraphs
>> 649379c Trac #21926: Deprecate unused stuff from sage/misc/misc.py
>> f9af853 Trac #21919: documentation of FiniteSetMaps(n) says it is over
>> {1, 2, ..., n}
>> e2729c8 Trac #21913: LatticePoset: Add certicate for
>> is_vertically_decomposable
>> 1ca5b30 Trac #21908: Fix _ascii_art_ for 0 in a CombinatorialFreeModule
>> 1b2e37c Trac #21607: Posets: with_linear_extension() and wrong constructor
>> 4c9e162 Trac #21513: Package rst2ipynb
>> c4df8bb Trac #17147: Overriding checks to generate poset and lattice
>> faster
>> aa2bcc1 Updated SageMath version to 7.5.beta4
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to sage-release+unsubscr...@googlegroups.com
>> .
>> To post to this group, send email to sage-release@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post

Re: [sage-release] Re: Sage 7.5.rc3 released

[Erik Bray]

I got a few non-obvious test failures on the Docker container built for this RC:

sage -t --long /opt/sage/src/sage/doctest/test.py
**
File "/opt/sage/src/sage/doctest/test.py", line 218, in sage.doctest.test
Failed example:
os.kill(pid, signal.SIGHUP)  # long time; 25 seconds passed => dead
Expected:
Traceback (most recent call last):
...
OSError: ...
Got:

**

sage -t --long /opt/sage/src/sage/interfaces/tests.py
**
File "/opt/sage/src/sage/interfaces/tests.py", line 42, in sage.interfaces.tests
Failed example:
subprocess.call("echo syntax error | Singular", **kwds)
Expected:
0
Got:
2
**

sage -t --long /opt/sage/src/sage/libs/gap/element.pyx
Bad exit: 2
**
Tests run before process (pid=14289) failed:
sage: libgap({'a': 1, 'b':123})   # indirect doctest ## line 88 ##

**

sage -t --long /opt/sage/src/sage/libs/gap/util.pyx
Bad exit: 2
**
Tests run before process (pid=14307) failed:
sage: from sage.libs.gap.util import ObjWrapper ## line 30 ##
sage: x = ObjWrapper() ## line 31 ##
sage: y = ObjWrapper() ## line 32 ##
sage: x == y ## line 33 ##
True
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## line 35 ##
0
sage: from sage.libs.gap.util import ObjWrapper ## line 53 ##
sage: x = ObjWrapper() ## line 54 ##
sage: y = ObjWrapper() ## line 55 ##
sage: x == y ## line 56 ##
True
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## line 58 ##
0
sage: from sage.libs.gap.util import ObjWrapper ## line 83 ##
sage: x = ObjWrapper() ## line 84 ##
sage: hash(x) ## line 85 ##
0
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## line 87 ##
0
sage: from sage.libs.gap.util import gap_root ## line 155 ##
sage: gap_root()   # random output ## line 156 ##
'/opt/sage/local/gap/latest'
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ##
line 158 ##
0
sage: libgap(123)   # indirect doctest ## line 177 ##

**
sage -t --long /opt/sage/src/sage/libs/gap/assigned_names.py
**
File "/opt/sage/src/sage/libs/gap/assigned_names.py", line 59, in
sage.libs.gap.assigned_names.load_or_compute
Failed example:
workspace(name='globals')
Expected:
('...', True)
Got:
('/home/sage/.sage/gap/libgap-globals-5920393023770190458', False)
**

sage -t --long /opt/sage/src/sage/tests/cmdline.py
**
File "/opt/sage/src/sage/tests/cmdline.py", line 558, in
sage.tests.cmdline.test_executable
Failed example:
err
Expected:
''
Got:
'Singular : signal 11 (v: 4100):\ncurrent
line:>>12345*54321;<<\nSegment fault/Bus error occurred at
7f0928854980 because of 10206 (r:1483960627)\nplease inform the
authors\ntrying to restart...\nfatal flex scanner internal error--end
of buffer missed\n'
**
File "/opt/sage/src/sage/tests/cmdline.py", line 560, in
sage.tests.cmdline.test_executable
Failed example:
ret
Expected:
0
Got:
2
**

Although the miscellaneous "Bad exit" statuses are similar to Justin's
report.  I don't know what this means.

Also this is the first RC of 7.5 I've tested on Docker, but I think
these are all new since 7.4 IIRC.

On Mon, Jan 9, 2017 at 1:51 AM, Justin C. Walker  wrote:
>
> On Jan 8, 2017, at 15:23 , John H Palmieri wrote:
>
>> Builds for me on OS X. I'm getting some random doctesting errors, for
>> example
>>
>>sage -t --long --warn-long 70.8 src/sage/coding/codecan/codecan.pyx  #
>> Bad exit: 2
>>
>> but they are not repeatable.
>
> I am able to build successfully on macOS 10.11.6, and testing ('ptestlong') 
> completes without problems!
> This was with "-j6" on a Quad-core Core i7.
>
> Justin
>
> --
> Justin C. Walker, Curmudgeon at Large
> Institute for the Absorption of Federal Funds
> ---
> If it weren't for carbon-14, I wouldn't date at all.
> ---
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/

Re: [sage-release] Re: Why is gcc built?

[Erik Bray]

On Wed, Feb 22, 2017 at 5:13 PM, Simon King  wrote:
> PS:
>
> On 2017-02-22, Simon King  wrote:
>>  Aha. Although I did "apt-get install gcc-fortran", gfortran is not there.
>
> And the reason is that apparently I didn't read the development manual
> with enough care. It advises to install gfortran (resp gcc-gfortran on
> redhat), and probably I tried gcc-fortran instead (which has failed, so,
> I really wonder why I didn't notice).
>
> Anyway, I now have SageMath on yet another laptop, and am looking
> forward to SageDays!

I've been bitten by the gfortran thing a couple times before.  IIRC
the main reason Sage started building its own gcc in the first place
was to get around bugs on OSX. But it stuck around and has since been
used to add its own version of gcc in cases where the user's gcc was
too old as well (due to bugs in that older gcc).

IMHO building Sage should not just forge ahead with building its own
gcc without asking.  I think it's bad enough that it's a package at
all, but as long as it is it should be strictly optional, and if the
version check fails for gcc/gfortran the build should just refuse to
continue (i.e. `./configure` would exit with an error) providing
information on what version checks were performed, what failed, and
mention that if desired sage can be built --with-gcc or something in
which case it will add gcc to the build.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Why is gcc built?

[Erik Bray]

On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik  wrote:
> one can still have something like:
> --with-everything  # build everything
> --with-everythingneeded # build missing
> etc...
> to encode the most usual cases.

Yes, I think this goes without saying.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Why is gcc built?

[Erik Bray]

On Fri, Feb 24, 2017 at 10:49 AM, Jeroen Demeyer  wrote:
> On 2017-02-24 10:31, Erik Bray wrote:
>>
>> On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik  wrote:
>>>
>>> one can still have something like:
>>> --with-everything  # build everything
>>> --with-everythingneeded # build missing
>>> etc...
>>> to encode the most usual cases.
>>
>>
>> Yes, I think this goes without saying.
>
>
> And why should --with-everythingneeded *not* be the default?

I don't particularly care what the default is but the point here in
the first place is that it shouldn't try to build and install its own
gcc if one doesn't explicitly ask for it, opting instead to report
what dependencies were missing such that sage couldn't be built.

I think Simon's point was that if it can be made to work that way for
gcc why stop there?  Admittedly gcc is a special case.  But one way or
another it would be good in general to have more control over what
packages Sage automatically builds and installs, as opposed to
requiring dependencies from the system--this is nothing new.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Why is gcc built?

[Erik Bray]

On Fri, Feb 24, 2017 at 7:06 PM, William Stein  wrote:
> On Fri, Feb 24, 2017 at 4:31 AM, Erik Bray  wrote:
>
>> I don't particularly care what the default is but the point here in
>> the first place is that it shouldn't try to build and install its own
>> gcc if one doesn't explicitly ask for it, opting instead to report
>> what dependencies were missing such that sage couldn't be built.
>>
>> I think Simon's point was that if it can be made to work that way for
>> gcc why stop there?  Admittedly gcc is a special case.  But one way or
>> another it would be good in general to have more control over what
>> packages Sage automatically builds and installs, as opposed to
>> requiring dependencies from the system--this is nothing new.
>
> "This is nothing new" for **most** projects.  For Sage this is.  From
> the very beginning I took an unusual approach to the Sage build system
> for various reasons -- mainly, so that mathematicians -- rather than
> software engineers -- could actually help with development.

When I wrote "this is nothing new" I just meant we've had this
discussion a dozen times just since I started working on the project,
not to mention for years before then (I remember it's partly what made
me interested in the first place).

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Why is gcc built?

[Erik Bray]

On Fri, Feb 24, 2017 at 3:38 PM, Jeroen Demeyer  wrote:
> On 2017-02-24 13:31, Erik Bray wrote:
>>
>> I don't particularly care what the default is
>
>
> You do care because you think it's not right that GCC is automatically
> installed when needed. Maybe you want the default to be

Fair enough--I do care when it comes to build dependencies,
*especially* GCC.  I don't feel as strongly when it comes to runtime
dependencies.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6 released

[Erik Bray]

On Sat, Mar 25, 2017 at 4:11 PM, Volker Braun  wrote:
> The "master" git branch has been updated to Sage-7.6. As always, you can get
> the latest beta version from the "develop" git branch. Alternatively, the
> self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> There was no change over 7.6.rc2

I'm going ahead and pushing the docker image for 7.6.  Not all the
tests pass, but that hasn't been the case for the last couple releases
in Docker.

I hope to get to the bottom of those test failures eventually.  I
think most of them are just failures due to test ordering...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.0.beta5 released

[Erik Bray]

Builds ok on Cygwin plus my additional patches for as yet unresolved
tickets.  Test results pending.

On Fri, May 5, 2017 at 12:40 PM, Henri Girard  wrote:
> ubuntu xenial ok
>
>
> Le 05/05/2017 à 12:06, Emmanuel Charpentier a écrit :
>
> On Debian testing running on Core i7+16 Gb RAM, same results as those
> reported for beta4.
>
> HTH,
>
> --
> Emmanuel Charpentier
>
> Le jeudi 4 mai 2017 23:49:33 UTC+2, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>>
>> 46a728a Updated SageMath version to 8.0.beta5
>> 33e0bd6 Trac #22912: issue with is_tree when the graph has loops
>> 5431a8f Trac #22905: py3: cleanup of test_strict_weak_order
>> d01e774 Trac #22904: numerical noise in
>> sage/matrix/matrix_double_dense.pyx
>> fa83bdc Trac #22903: rich comparison for ideals in fin dim algebras
>> c4098ddc Trac #22902: cleanup of galois_group.py
>> 560815f Trac #22899: backport some doctests from cypari2
>> 8c25b32 Trac #22892: py3 : about range in homology folder
>> 0a23b06 Trac #22891: Add giac interface to integrate
>> 33acd76 Trac #22887: py3 forbids inspect.currentframe(1)
>> 2204f76 Trac #22930: Fixed broken install of Python 2 and 3 on Cygwin
>> since #22764
>> 03df34c Trac #22880: Simplicial complexes: bug in add_face
>> 3c7f290 Trac #22901: Poset: Add crosslinks to weaker and stronger
>> properies
>> 509231e Trac #22898: has_perfect_matching for graphs
>> 9198785 Trac #22897: QuotientRing_nc.ideal() should not call
>> CommutativeRing.ideal
>> a777522 Trac #22867: LatticePoset: Reverse completion_by_cuts()
>> 6adf7eb Trac #22861: Implement Adams operation on group characters
>> ad9cf6a Trac #22828: py3: rich comparison for asymptotic term monoid
>> 5a1a3fc Trac #22893: unicode art for chain complexes
>> fe5e2f7 Trac #22847: Improve the style of headings of Sage files
>> 911a759 Trac #22826: Test failure in sage.functions.orthogonal_polys when
>> Singular is built with SAGE_DEBUG=yes
>> 3b86fa9 Trac #22882: Fix e_string_to_ground_state for type A2 even dual
>> fadea82 Trac #22881: py3: handle type "long" in sage_input
>> 2397568 Trac #22879: py3: use six.integer_types (step 2/2)
>> 4f5fe17 Trac #22868: Update Singular to 4.1.0p3
>> 0b60c05 Trac #22859: Do not check for a zero result in arithmetics of
>> coordinate functions and scalar fields
>> fd3e5b1 Trac #22748: Provide yasm on i386 + x86_64 systems
>> 43be68d Trac #22582: Install pip into py2 + py3 and fix py3 dependencies
>> build
>> 6325b02 Trac #21416: Add jupyter-kernel-gap package
>> 23f33ec Trac #22885: Fix issue in average_distance
>> 85f3597 Trac #22884: Incorrectly computed precision with leading zeros and
>> decimal point
>> b399883 Trac #22878: Add gmp to libraries for libs/ecl and rings/bernmm
>> 4d91c17 Trac #22876: py3: replace StringTypes by six.string_types
>> cb934ae Trac #22874: py3: 2 bad calls ot iteritems
>> 139149e Trac #22871: py3: use six.integer_types (step 1/2)
>> 0e16e41 Trac #22870: Update ore_algebra to 0.3
>> 4d6ae38 Trac #22869: Update NTL to 10.3.0
>> 90d9b57 Trac #22823: Symbolic asin/acos do not return symbolic NaN
>> 0605d26 Trac #22756: Python3 is broken on OS X
>> 47e8e1c Trac #22668: HTML widget without description
>> 6cf09ab Trac #20730: Break up sage_setup.autogen.interpreters into a
>> package
>> 42901bc Trac #19439: Corrections to infinities returned by mpmath
>> 6b9461b Trac #22856: Upgrade libhomfly
>> 7177ef5 Updated SageMath version to 8.0.beta4
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.0.beta6 released

[Erik Bray]

Looks good on Cygwin, with patches for the few remaining blockers [1]
applied on top.

Thanks,
Erik

[1] 
https://trac.sagemath.org/query?priority=blocker&status=needs_info&status=needs_review&status=needs_work&status=new&status=positive_review&component=porting%3A+Cygwin&col=id&col=summary&col=component&col=priority&col=status&col=type&col=milestone&order=priority

On Sat, May 13, 2017 at 11:04 AM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
>
> df03447 Updated SageMath version to 8.0.beta6
> 86557bd Trac #22729: Expose some internal variables computed in hecke_series
> f14995b Trac #21993: Polyhedron.integral_points(): OverflowError: value too
> large to convert to int
> 3c79df8 Trac #21668: sage.stats.basic_stats.mode doesn't sort
> 476ef25 Trac #19139: Implement categories for KR crystals
> 540e6b9 Trac #17505: implement symbolic product
> 2208923 Trac #22939: fixing a typo
> 068b093 Trac #22674: Add irreducibles_poset()
> dd7d64f Trac #22877: Wrong atan2 of complex arguments
> 263e6d1 Trac #22773: Add random Stone lattice
> 755298b Trac #22684: pynormaliz fails to build on 32bit system
> 7c5814b Trac #19075: Speedup creation of Kleber tree
> 4ee6131 Trac #22923: Fix documentation regarding cached functions in the
> Steenrod algebra code
> 643ded5 Trac #22940: another typo
> c2e84e2 Trac #22925: Fix Cython interface to Pynac's find_function
> 7aa9ec8 Trac #22911: Reorganize some methods for loops
> 3d17975 Trac #22906: improve add_clique to allow various iterable container
> 21e33f7 Trac #22950: combinat/posets/posets.py fails when the optional
> package dot2tex is installed
> b238720 Trac #22948: avoid "absolute_import" in tab completion
> ef9d7e0 Trac #22943: Speedup rigged configuration bijection in type B
> 5918bf2 Trac #22938: Polytopes normaliz backend doesn't handle a polytope
> with a trivial integral hull
> 437154d Trac #22933: clean up deprecations in sandpile
> c00fe01 Trac #22932: py3: remove one call to unicode in
> src/sage_setup/docbuild/__init__.py
> f4e91c4 Trac #22931: Add missing sphinx labels to prep and other tutorials
> 4d60046 Trac #22919: py3: some care for cmp in monoids folder
> 2603c91 Trac #22929: Followup to #22666
> b259b4c Trac #22910: Polynomial ring when is_field is NotImplemented
> 9afa2a0 Trac #22642: Cythonize tensor product of crystals elements
> 77a9ab3 Trac #22429: Some cleanup of the crystals files
> 5d5c8fb Trac #21386: HochschildComplex does not pass its testsuite
> 4410a16 Trac #18655: MV Polytopes and PBW crystals
> ff9499e Trac #18303: faster comparisons in AA and QQbar
> 46a728a Updated SageMath version to 8.0.beta5
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.0.beta6 released

[Erik Bray]

On Mon, May 15, 2017 at 1:46 PM, Erik Bray  wrote:
> Looks good on Cygwin, with patches for the few remaining blockers [1]
> applied on top.

Actually, now I'm having a problem with the sage/libs/ecl.pyx tests,
which strangely did not have any problems on my original test run on
beta6.  Previously it ran in ~4.5 seconds with no problem, but now I'm
getting:

sage -t --long --warn-long 188.3 src/sage/libs/ecl.pyx
Timed out (with segmentation fault after interrupt)
**
Tests run before process (pid=2952) timed out:
sage: from sage.libs.ecl import test_sigint_before_ecl_sig_on ## line 112 ##
sage: test_sigint_before_ecl_sig_on() ## line 113 ##
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ##
line 117 ##
0
sage: from sage.libs.ecl import test_ecl_options ## line 134 ##
sage: test_ecl_options() ## line 135 ##
ECL_OPT_INCREMENTAL_GC = 0
ECL_OPT_TRAP_SIGSEGV = 1
ECL_OPT_TRAP_SIGFPE = 1
ECL_OPT_TRAP_SIGINT = 1
ECL_OPT_TRAP_SIGILL = 1
ECL_OPT_TRAP_SIGBUS = 1
ECL_OPT_TRAP_SIGCHLD = 0
ECL_OPT_TRAP_SIGPIPE = 1
ECL_OPT_TRAP_INTERRUPT_SIGNAL = 1
ECL_OPT_SIGNAL_HANDLING_THREAD = 0
ECL_OPT_SIGNAL_QUEUE_SIZE = 16
ECL_OPT_BOOTED = 1
ECL_OPT_BIND_STACK_SIZE = 8192
ECL_OPT_BIND_STACK_SAFETY_AREA = 1024
ECL_OPT_FRAME_STACK_SIZE = 2048
ECL_OPT_FRAME_STACK_SAFETY_AREA = 128
ECL_OPT_LISP_STACK_SIZE = 32768
ECL_OPT_LISP_STACK_SAFETY_AREA = 128
ECL_OPT_C_STACK_SIZE = 1048576
ECL_OPT_C_STACK_SAFETY_AREA = 32768
ECL_OPT_SIGALTSTACK_SIZE = 1
ECL_OPT_HEAP_SIZE = 4294967296
ECL_OPT_HEAP_SAFETY_AREA = 1048576
ECL_OPT_THREAD_INTERRUPT_SIGNAL = 0
ECL_OPT_SET_GMP_MEMORY_FUNCTIONS = 0
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ##
line 161 ##
0
sage: from sage.libs.ecl import * ## line 223 ##
sage: init_ecl() ## line 228 ##
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ##
line 232 ##
0
sage: from sage.libs.ecl import * ## line 326 ##
sage: from cysignals.tests import interrupt_after_delay ## line 327 ##
sage: ecl_eval("(setf i 0)") ## line 328 ##

sage: inf_loop = ecl_eval("(defun infinite() (loop (incf i)))") ## line 330 ##
sage: interrupt_after_delay(1000) ## line 331 ##
sage: inf_loop() ## line 332 ##



> On Sat, May 13, 2017 at 11:04 AM, Volker Braun  wrote:
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>>
>> df03447 Updated SageMath version to 8.0.beta6
>> 86557bd Trac #22729: Expose some internal variables computed in hecke_series
>> f14995b Trac #21993: Polyhedron.integral_points(): OverflowError: value too
>> large to convert to int
>> 3c79df8 Trac #21668: sage.stats.basic_stats.mode doesn't sort
>> 476ef25 Trac #19139: Implement categories for KR crystals
>> 540e6b9 Trac #17505: implement symbolic product
>> 2208923 Trac #22939: fixing a typo
>> 068b093 Trac #22674: Add irreducibles_poset()
>> dd7d64f Trac #22877: Wrong atan2 of complex arguments
>> 263e6d1 Trac #22773: Add random Stone lattice
>> 755298b Trac #22684: pynormaliz fails to build on 32bit system
>> 7c5814b Trac #19075: Speedup creation of Kleber tree
>> 4ee6131 Trac #22923: Fix documentation regarding cached functions in the
>> Steenrod algebra code
>> 643ded5 Trac #22940: another typo
>> c2e84e2 Trac #22925: Fix Cython interface to Pynac's find_function
>> 7aa9ec8 Trac #22911: Reorganize some methods for loops
>> 3d17975 Trac #22906: improve add_clique to allow various iterable container
>> 21e33f7 Trac #22950: combinat/posets/posets.py fails when the optional
>> package dot2tex is installed
>> b238720 Trac #22948: avoid "absolute_import" in tab completion
>> ef9d7e0 Trac #22943: Speedup rigged configuration bijection in type B
>> 5918bf2 Trac #22938: Polytopes normaliz backend doesn't handle a polytope
>> with a trivial integral hull
>> 437154d Trac #22933: clean up deprecations in sandpile
>> c00fe01 Trac #22932: py3: remove one call to unicode in
>> src/sage_setup/docbuild/__init__.py
>> f4e91c4 Trac #22931: Add missing sphinx labels to prep and other tutorials
>> 4d60046 Trac #22919: py3: some care for cmp in monoids folder
>> 2603c91 Trac #22929: Followup to #22666
>> b259b4c Trac #22910: Polynomial ring when is_field is NotImplemented
>> 9afa2a0 Trac #22642: Cythonize tensor product of crystals elements
>> 77a9ab3 Trac #22429: Some cleanup of the crystals files
>> 5d5c8fb Trac #21386: HochschildComplex does not pass its testsuite
>> 4410a16 Trac #18655: MV Polytopes and PBW crystals
>> ff9499e Trac #18303: faster comparisons in AA and QQbar
>> 46a728a U

Re: [sage-release] Sage 8.0.beta7 released

[Erik Bray]

ECM build fails on Cygwin:

[ecm-7.0.4.p0] checking for DLL/static GMP... DLL
[ecm-7.0.4.p0] configure: error: gmp.h is a DLL: use --disable-static
--enable-shared
[ecm-7.0.4.p0] Error configuring GMP-ECM.
[ecm-7.0.4.p0] (See above for the options passed to its 'configure'.)

I don't know why it doesn't get the right flags in the first place,
but I do see some bits about that in the spkg-install, which I haven't
looked closely at.  I also don't know why it thinks "gmp.h is a DLL"
but I'm guessing that's just a poorly worded message.


On Thu, May 18, 2017 at 9:46 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> 7a36941 Updated SageMath version to 8.0.beta7
> 6eda482 Trac #22994: Use permutation implementation of Weyl groups to
> compute LS path energy
> e6585df Trac #22209: Differentiation of conj/imag/real/abs functions
> 51f8023 Trac #21819: Rewrite error functions and documentation
> ff3ad80 Trac #22987: bug in cardinality of vector space
> 8d9cb28 Trac #22957: Faster implementation for has_perfect_matching
> 127bae7 Trac #22942: update python3 spkg to version 3.6.1
> 49a6db9 Trac #22907: py3: phase out lexico cmp in real_mpfi
> 5abdee9 Trac #22890: py3: change doc for comparison in element classes
> e2f78a6 Trac #22815: py3: caring for cmp in combinat/combinat
> b334f08 Trac #22796: Remove deprecated_callable_import
> 7cfe9f6 Trac #22745: LatticePoset: "antidoubling", part 3
> 8315100 Trac #21580: Coxeter3 does not pass self checks
> ced0af2 Trac #20915: Plotting Set Partitions as Chord Diagrams
> c658fcf Trac #19838: Doctest: make logarithm to some base in real ball field
> work
> a187e7b Trac #15253: Cartesian product of polyhedra with different dimension
> fails
> c240d86 Trac #22993: some care for SEEALSO
> 37d83dc Trac #22977: a bunch of typos
> 2e4f104 Trac #22954: Generator of Windmill graphs
> 103a653 Trac #22952: Trivial failure in py3_syntax test
> b596c6b7 Trac #22941: Fix error in Sage's rich output display formatter
> d60ca37 Trac #22935: LatticePoset: join-pseudocomplemented & some links
> e703e28 Trac #22865: Modifying coding thematic tutorial imports
> e150c2e Trac #16561: Derivations for separable function fields
> 5a72c8a Trac #22916: py3 use six.string_types in a few places
> 89e7273 Trac #22844: Symbolic limit
> 179021f Trac #22833: fix a calculus doctest (giac, laplace, integration)
> 399aae1 Trac #22981: py3: get rid of cmp() in element.pyx
> 106fab3 Trac #22980: py3: get rid of cmp in coerce.pyx
> 5e6cc9a Trac #22973: py3: some care for cmp in units and interfaces
> 5c74053 Trac #22972: py3: some more care for range
> 140c85c Trac #22953: Add "sage --python3" command
> ac60d14 Trac #22944: remove experimental warning of asymptotic ring
> bcd6b7f Trac #22937: Implement a "distribute" method
> 5a15fb0 Trac #22936: Newton polygon of polynomials over power series with
> infinite precision
> a4c2335 Trac #22924: cleaning of linbox for dense integer matrices
> b54d40b Trac #22918: py3: do not use basestring
> 6ee224a Trac #20385: Update GMP-ECM to version 7.0
> 1d9e2a5 Trac #18212: fix NameError in mathematica_free integration
> d79ff53 Trac #11759: octahedron() and icosahedron() produce "non-enclosed"
> polyhedra
> df03447 Updated SageMath version to 8.0.beta6
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.0.beta7 released

[Erik Bray]

On Fri, May 19, 2017 at 9:57 AM, Erik Bray  wrote:
> ECM build fails on Cygwin:
>
> [ecm-7.0.4.p0] checking for DLL/static GMP... DLL
> [ecm-7.0.4.p0] configure: error: gmp.h is a DLL: use --disable-static
> --enable-shared
> [ecm-7.0.4.p0] Error configuring GMP-ECM.
> [ecm-7.0.4.p0] (See above for the options passed to its 'configure'.)
>
> I don't know why it doesn't get the right flags in the first place,
> but I do see some bits about that in the spkg-install, which I haven't
> looked closely at.  I also don't know why it thinks "gmp.h is a DLL"
> but I'm guessing that's just a poorly worded message.

Forcing the suggested flags fixed this.  But the build fails later due
to a bug in Linbox:

[sagelib-8.0.beta7] In file included from
../local/include/linbox/algorithms/bbcharpoly.h:45:0,
[sagelib-8.0.beta7]  from
../local/include/linbox/solutions/charpoly.h:34,
[sagelib-8.0.beta7]  from
build/cythonized/sage/libs/linbox/linbox_flint_interface.cpp:572:
[sagelib-8.0.beta7] ../local/include/linbox/solutions/det.h: In
function ‘typename Blackbox::Field::Element& LinBox::det(typename
Blackbox::Field::Element&, const Blackbox&, const
LinBox::RingCategories::ModularTag&, const Wiedemann&)’:
[sagelib-8.0.beta7] ../local/include/linbox/solutions/det.h:239:39:
error: expected unqualified-id before numeric constant
[sagelib-8.0.beta7]  Compose > B0 (&A, &D);

Funny because this is the second time Linbox has had this bug--using
"B0" as a variable name is a no-go since it's a standard macro defined
in  [1] which, for implementation-specific reasons, might
happen to be pulled in by an include.

[1] http://pubs.opengroup.org/onlinepubs/009695399/basedefs/termios.h.html

> On Thu, May 18, 2017 at 9:46 PM, Volker Braun  wrote:
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> 7a36941 Updated SageMath version to 8.0.beta7
>> 6eda482 Trac #22994: Use permutation implementation of Weyl groups to
>> compute LS path energy
>> e6585df Trac #22209: Differentiation of conj/imag/real/abs functions
>> 51f8023 Trac #21819: Rewrite error functions and documentation
>> ff3ad80 Trac #22987: bug in cardinality of vector space
>> 8d9cb28 Trac #22957: Faster implementation for has_perfect_matching
>> 127bae7 Trac #22942: update python3 spkg to version 3.6.1
>> 49a6db9 Trac #22907: py3: phase out lexico cmp in real_mpfi
>> 5abdee9 Trac #22890: py3: change doc for comparison in element classes
>> e2f78a6 Trac #22815: py3: caring for cmp in combinat/combinat
>> b334f08 Trac #22796: Remove deprecated_callable_import
>> 7cfe9f6 Trac #22745: LatticePoset: "antidoubling", part 3
>> 8315100 Trac #21580: Coxeter3 does not pass self checks
>> ced0af2 Trac #20915: Plotting Set Partitions as Chord Diagrams
>> c658fcf Trac #19838: Doctest: make logarithm to some base in real ball field
>> work
>> a187e7b Trac #15253: Cartesian product of polyhedra with different dimension
>> fails
>> c240d86 Trac #22993: some care for SEEALSO
>> 37d83dc Trac #22977: a bunch of typos
>> 2e4f104 Trac #22954: Generator of Windmill graphs
>> 103a653 Trac #22952: Trivial failure in py3_syntax test
>> b596c6b7 Trac #22941: Fix error in Sage's rich output display formatter
>> d60ca37 Trac #22935: LatticePoset: join-pseudocomplemented & some links
>> e703e28 Trac #22865: Modifying coding thematic tutorial imports
>> e150c2e Trac #16561: Derivations for separable function fields
>> 5a72c8a Trac #22916: py3 use six.string_types in a few places
>> 89e7273 Trac #22844: Symbolic limit
>> 179021f Trac #22833: fix a calculus doctest (giac, laplace, integration)
>> 399aae1 Trac #22981: py3: get rid of cmp() in element.pyx
>> 106fab3 Trac #22980: py3: get rid of cmp in coerce.pyx
>> 5e6cc9a Trac #22973: py3: some care for cmp in units and interfaces
>> 5c74053 Trac #22972: py3: some more care for range
>> 140c85c Trac #22953: Add "sage --python3" command
>> ac60d14 Trac #22944: remove experimental warning of asymptotic ring
>> bcd6b7f Trac #22937: Implement a "distribute" method
>> 5a15fb0 Trac #22936: Newton polygon of polynomials over power series with
>> infinite precision
>> a4c2335 Trac #22924: cleaning of linbox for dense integer matrices
>> b54d40b Trac #22918: py3: do not use basestring
>> 6ee224a Trac #20385: Update GMP-ECM to version 7.0
>> 1d9e2a5 Trac #18212: fix NameError in mathematica_free integration
>> d79ff53

Re: [sage-release] Sage 8.0.beta8 released

[Erik Bray]

On Wed, May 24, 2017 at 11:49 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html

LGTM on Cygwin, modulo https://trac.sagemath.org/ticket/23083 and the
previous blockers.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.0.rc0 released

[Erik Bray]

Any chance someone can give me review on the following tickets:

https://trac.sagemath.org/ticket/21233
https://trac.sagemath.org/ticket/23097

?

The first fixes the one consistently failing test on Cygwin.  Florent
reviewed it once a long time ago and had some comments, but I believe
I've addressed his comments (I could be wrong there but I think the
code is fine as is).

The second fixes a bug that doesn't show up in any tests, but can
still lead to severe disk cluttering over time.

Thanks,
Erik

On Thu, Jun 29, 2017 at 11:24 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
>
> 7de256c Updated SageMath version to 8.0.rc0
> 226bb83 Trac #15994: Python 3 preparation: Change for removed members of
> types module
> 9a0cfac Trac #23294: Do not use modules without cimporting (part 2)
> 439836f Trac #23107: py3: fix everything in src/sage/matrix/*
> f4b8a94 Trac #22297: py3 remove __cmp__ from Element
> 8abee3a Trac #19573: Natural coercion from Integers(p*k) to GF(p) for prime
> p
> f1c959d Trac #17039: Allow IndexedGenerators to handle `names`
> 5928a38 Trac #23208: Enhanced backtrace on test timeout
> 64ec36c Trac #23290: Graph.merge_vertices() destroys loops
> 0fcfddc Trac #22777: Animate in Jupyter notebook
> 99ac16f Trac #23289: polymake does not build with gcc.7.1
> ede52b6 Trac #23308: Remove unused variable from RealNumber object
> 273a2af Trac #23306: Do not change Singular includes
> 34ea4af Trac #22277: change ring multivariate Laurent Polynomials
> 5a4cbef Trac #23323: use string types in Cartan factory
> 5fe4415 Trac #23317: NULL result without error while sorting words
> 52fb56e Trac #23314: Ignored exceptions in glpk_backend.pyx
> e7ea799 Trac #23305: py3: work on cmp in fraction fields and orders in
> number fields
> e661e6c Trac #23303: py3: get rid of cmp for species and yang-baxter
> 5392dd6 Trac #23302: Fix pickling of UniqueFactory elements with Cython 0.26
> a467d23 Trac #23301: py3: some care for cmp in some modular files
> ced02e9 Trac #23262: Enable png support in giac
> 31268b9 Trac #23248: sympy behavior depends on gmpy2 installation
> fa8cb83 Trac #23226: py3: some care for cmp in schemes
> f58d4e8 Trac #23159: Deprecation from #5930 should not use inspect
> 82df171 Trac #23093: Doctest fixes for bugs with real_part and is_real
> 1e5f842 Trac #23067: Upgrade R to 3.4.0
> 8236443 Trac #18700: Use GroupAlgebra as the standard class for group
> algebras
> 005c29b Trac #17554: Univariate Laurent polynomial do not properly handle
> __call__
> ce5653b Trac #16516: Faster roots computation for sparse polynomials over ZZ
> ec4b5bb Trac #15484: Implement Yangian for gl(n)
> 56d1543 Trac #19974: document "sage --notebook=jupyter"
> afeb0d6 Updated SageMath version to 8.0.beta12
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.0.rc1 released

[Erik Bray]

On Thu, Jul 6, 2017 at 12:52 AM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> c522ced Updated SageMath version to 8.0.rc1
> c276485 Trac #23339: Fixes to the sage-rebaseall.sh script (followup to
> #20986)
> 610bfde Trac #21399: Provide ctypes.util.find_library compatibility with
> Cygwin
> 97a8bdf Trac #23284: Testing padic_base_leaves.py takes a VERY long time
> 7de256c Updated SageMath version to 8.0.rc0

Since 2/3 of these fixes are for Cygwin, I'll just confirm that the
Cygwin builds (and, usually, the tests too) are now quite stable, at
least for me (though I've also gotten some positive feedback from
Emmanuel).

I think there are still some occasional problems with DLL rebasing,
especially in parallel builds.  I plan to work on resolving that, but
I don't think it's critical at the moment.

Thanks,
Erik

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.beta3 released

[Erik Bray]

On Wed, Aug 23, 2017 at 10:44 AM, Emmanuel Charpentier
 wrote:
> On Debian testing running on Core i7 + 16 GB RAM (MAKE="make -j8"), passes
> ptestlong with one failure :
>
> --
> sage -t --long src/sage/rings/function_field/function_field.py  # Timed out
> --
>
> which passes with no failure (but needs 669.8 seconds (!))  when ran
> standalone.
>
> For comparison, the same test , called by "make ptestlong" on a slightly
> smaller macine (Debian on Core i3 + 8 GB RAM, MAKE="make -j4") took 817.25
> seconds (and did not reach the timeout limit...).
>
> Hypothesis : ptestlong's computation of the timeout limit is more
> conservative on the "smaller" machine.

I'm also having problems with this test in my attempt to build a
docker image for 8.1.beta3.  It is failing consistently with a
timeout.  I also get a long C stack trace at:

sage: TestSuite(N).run(skip = '_test_derivation')  # long time ## line 70 ##

/opt/sage/local/lib/python2.7/site-packages/cysignals/signals.so(+0x5ca8)[0x7f837bfbcca8]
/opt/sage/local/lib/python2.7/site-packages/cysignals/signals.so(+0x5d15)[0x7f837bfbcd15]
/opt/sage/local/lib/python2.7/site-packages/cysignals/signals.so(+0x8e07)[0x7f837bfbfe07]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7f8380d56d10]
/opt/sage/local/lib/libpython2.7.so.1.0(PyDict_GetItem+0x1c)[0x7f838100160c]
/opt/sage/local/lib/libpython2.7.so.1.0(_PyType_Lookup+0x5f)[0x7f838102863f]
/opt/sage/local/lib/libpython2.7.so.1.0(_PyObject_GenericGetAttrWithDict+0x75)[0x7f8381007975]
/opt/sage/local/lib/python2.7/site-packages/sage/structure/category_object.so(+0x620f)[0x7f837496620f]
/opt/sage/local/lib/python2.7/site-packages/sage/rings/polynomial/polynomial_zz_pex.so(+0x2c584)[0x7f8142e31584]
...

where I guess the signal that's being handled is a SIGALRM.

I can post the full stack trace if anyone thinks it will be useful but
it seems like we already have an idea what's wrong here...



> Le mardi 22 août 2017 00:23:40 UTC+2, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> 037272ccba (tag: 8.1.beta3) Updated SageMath version to 8.1.beta3
>> e5005bdf80 Trac #23622: LatticePoset doc, use the master bib file
>> e87f9b5ac6 Trac #19339: Use digraph labels if present for ClusterAlgebra
>> and ClusterQuiver
>> c8a96622b7 Trac #23654: Bug in ClusterAlgebra _coerce_map_from_
>> 8808ca4011 Trac #23651: py3 more cmp for polynomial ring elements
>> 03bad70bdc Trac #23649: py3 richcmp for Gamma congruence groups
>> 3b249bf9dc Trac #23641: py3: another load of absolute imports in cython
>> files
>> 8c4222beb7 Trac #23636: arccoth(float) returns complex
>> 6c8bd5d748 Trac #23633: infinite polynomial: iterate over
>> coefficient/monomial
>> 7f7f583875 Trac #23608: Riemann surfaces: homomorphisms, interfacing, sums
>> aff66a3b37 Trac #23583: py3: some more richcmp in schemes, rings, and
>> combinat
>> efaeac41d1 Trac #20932: Issues with p1list in modular symbols
>> af8f63c5b1 Trac #23624: 0 should not be a primitive root
>> e55b6ea474 Trac #23378: GradedCommutativeAlgebra constructor passes names
>> as NCPolynomial_plural
>> 5af5f731a4 Trac #23472: The error message for splitting_field when name is
>> None does not match that of NumberField
>> 689096eed8 Trac #23620: gcd has wrong parent
>> 8e2e4876b2 Trac #23609: Don't use wrong Cremona labels in elliptic_curves
>> database
>> 3cbfcdae00 Trac #23160: Add a library of common helper functions for use
>> in spkg-install
>> ae0118fcc7 Trac #7304: Contract edge in graph
>> f70241fb6c Trac #23617: Zq's default type  in the documentation didn't
>> agree with the code
>> d2f8470c67 Trac #23616: fmpz_mat_to_mpz_array ignores exceptions
>> 41836402a7 Trac #23605: Heisenberg group
>> 39f21c47d9 Trac #23379: LatticePoset: add adjunct()
>> effcedba41 (tag: 8.1.beta2) Updated SageMath version to 8.1.beta2
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visi

Re: [sage-release] Sage 8.1.beta4 released

[Erik Bray]

On Tue, Sep 5, 2017 at 8:37 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html

On Windows I'm getting a bunch of errors when building the docs like:

[dochtml] RuntimeError: ECL says: Memory limit reached. Please jump to
an outer pointer, quit program and enlarge the
[dochtml] memory limits before executing the program again.

but only when SAGE_NUM_THREADS > 1.  Didn't used to get this before
but it's disconcerting :/

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.beta7 released

[Erik Bray]

On Fri, Oct 13, 2017 at 9:38 AM, Sébastien Labbé  wrote:
> On a recent dell machine running Ubuntu 16.06, I get one failing test during
> make ptestlong. The test pass when run alone :
>
>
> sage -t --long src/sage/libs/gap/assigned_names.py
> **
> File "src/sage/libs/gap/assigned_names.py", line 59, in
> sage.libs.gap.assigned_names.load_or_compute
> Failed example:
> workspace(name='globals')
> Expected:
> ('...', True)
> Got:
> ('/home/slabbe/.sage/gap/libgap-globals-0x2d2b865d7c9d0d95', False)
> **
> 1 item had failures:
>1 of   5 in sage.libs.gap.assigned_names.load_or_compute
> [15 tests, 1 failure, 119.14 s]

This test randomly fails for me sometimes as well, but that has been
the case for a long time.  I think there's a ticket for it

Yep, here it is: https://trac.sagemath.org/ticket/20421

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.beta8 released

[Erik Bray]

On Tue, Oct 17, 2017 at 8:56 AM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> a2e82e15a2 (HEAD -> develop, tag: 8.1.beta8, trac/develop) Updated SageMath
> version to 8.1.beta8
> 7dc7c74d76 Trac #23872: Singular expansion for implicitly defined function
> 71c53d6efc Trac #23844: GapElement.__contains__ (from libgap) should use the
> infix `in` from gap
> 03398aa3f4 Trac #23818: py3: hash for complex interval fields
> 756c0ec447 Trac #23671: hypergeometric motives
> e7b4f77db7 Trac #22922: Faster implementation of LLT polynomials
> 8d71436074 Trac #20762: Several additional methods for SimplicialComplex
> 37b5b2cfd2 Trac #18236: support xz compressed tarballs
> 202fa8dd8c Trac #24020: Cygwin: misc test failures
> a56746c985 Trac #23922: Upgrade eclib to compile with xcode 9
> 1472db0a6b Trac #23985: rst2ipynb causes doctest failures if pandoc is not
> installed
> 067b87c610 Trac #23983: dot2tex breaks docbuild
> 11c3bcca4e Trac #23979: Ignore failure in setrlimit on Cygwin
> e96397a071 Trac #23973: doc build hangs on Cygwin
> c249d236cb Trac #22461: Implement cython() using cythonize()
> 50670a7181 Trac #7516: bug in pickling quotient module over pid
> fce8fd00d4 Trac #23997: installed_packages(False) gives wrong version for
> Python packages with patches
> cc5307 Trac #23976: giacpy_sage causes doctest failures due to threading
> a22a806a2d Trac #23975: sage-location: do not remove .pyc files
> 2c6ac6c343 Trac #23970: Simpler caching in ell_rational_field
> cda826dfaf Trac #23966: Conversion from ZpFM to its fraction field incorrect
> 4bce0bfd2d Trac #23965: Coercion to fraction field is injective
> c3b1b7780a Trac #23862: speed_up_left_and_right_key
> a1b45bb7c4 Trac #23839: Fix reference manual index for partn_ref
> 1b74aa24b0 Trac #23634: A base class for integral quadratic forms seen as
> modules with a bilinear form.
> 9659a399eb Trac #18395: (moderate) Speedup in layout_spring
> c4aef0e21f Trac #23962: rank() of elliptic curves should always consult
> Cremona database
> 78a2ebd287 Trac #23957: gmpy2 causes doctest failures
> 7d5784f2a9 Trac #23947: Reciprocal transformation and trace polynomial
> e5cb49e05c Trac #23800: Add O method for Laurent series rings
> 0e98d937dc Trac #23963: py3: richcmp for function field ideals
> 380c526205 Trac #23951: fix rotate and conjugate in growth diagrams
> 639646985c Trac #23905: Avoid _element_constructor in Homset
> a5eeff69d2 Trac #23949: py3 : some work on __cmp__ and richcmp
> b580a4c279 Trac #23929: Upgrade to cypari2 version 1.1.3
> 894facd65a Trac #23912: parent() is slow for non-Elements
> bda5b4d10b Trac #23925: Bulk fix of signal handling in symbolics
> 68cb85abe9 Trac #23713: Support SAGE_NUM_THREADS everywhere for parallellism
> 3c684b65ed Trac #23944: Q/Z
> 0d96592852 Trac #23932: differences in construction of PolynomialRing and
> LaurentPolynomialRing
> 35ffe56528 Trac #23915: include the inner_product_matrix in module
> comparison
> da6237b58e Trac #23883: InheritComparisonClasscallMetaclass.__new__() does
> not work
> 2e522cf00a Trac #23865: disable a very long doctest in omega.py
> b198ad5d04 Trac #23857: Implement conversion C++ <-> str
> 1a06cd5dd1 Trac #23815: Upgrade to Python 2.7.14
> 26a96021b2 Trac #23734: Implement iterator for generic permutations in
> Cython
> 5455b1ce78 Trac #23642: Factorization over some quotient rings incorrect
> 82260ab4ad Trac #23565: update arb to version 2.11.1
> c3f620e7b7 Trac #23544: Upgrade PARI/GP to git master version
> 75daefe5ed Trac #23510: Fraction field of fixed modulus p-adic rings should
> have floating point type
> f8b263fb53 Trac #23376: Equality testing of genera of quadratic forms over
> ZZ changes the genus and produces false results
> b0c0f6749a Trac #22886: fix pxd header files
> 54ba5948be Trac #23429: Multivector fields and the Schouten-Nijenhuis
> bracket
> c24da43be9 Trac #23131: Add computation of longest commons extensions in a
> word
> c1c3197fc3 Trac #22720: AdditiveAbelianGroup([]).annihilator() fails.
> 294c389e84 Trac #18386: Doctests for: fix polylog evalf
> cc613b1e98 (tag: 8.1.beta7) Updated SageMath version to 8.1.beta7

Tried to build the Docker image but am getting the following test
failure consistently (which did not occur in 8.1.beta7 AFAIK):

File "/opt/sage/src/sage/misc/sageinspect.py", line 207, in
sage.misc.sageinspect._extract_embedded_position
Failed example:

print(open(_extract_embedded_position(inspect.getdoc(test_funct))[1]).read())
Exception raised:
Traceback (most recent call last):
  File "/opt/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 515, in _run
self.compile_and_execute(example, compiler, test.globs)
  File "/opt/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 885, in compile_and_execute
exec(compiled, globs)
   

Re: [sage-release] Sage 8.1.beta8 released

[Erik Bray]

On Wed, Oct 18, 2017 at 4:59 PM, Jeroen Demeyer  wrote:
> Just to be clear: is this the *only* failure or are you seeing several
> similar failures (if so: please show them all).

(Assuming you're replying to me) No, just the one.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.beta8 released

[Erik Bray]

On Wed, Oct 18, 2017 at 5:29 PM, Jeroen Demeyer  wrote:
> On 2017-10-18 16:57, Erik Bray wrote:
>>
>> Any ideas?  Looks odd...
>
>
> Please try again with attached patch

Thanks, but no need--I think I see the issue.  If you happen to be
somewhere on the path of the cythonized file, then the "File" string
Cython produces ends up being relative to your current directory,
whereas _extract_embedded_position seems to assume the filename is
relative to the directory under SPYX_TMP.

The reason this happens in the Docker container is that it by default
starts out in /home/sage (the default user's home directory) and runs
the test suite from here as well, so the File string ends up being
relative to /home/sage instead.

It would probably be best if cython() change directory to target_dir
before calling cythonize()  (or if there's some way to force cythonize
to output an absolute filename that might be good too, but I don't
know if there's an easy way to do this).

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.beta8 released

[Erik Bray]

On Wed, Oct 18, 2017 at 9:54 PM, Jeroen Demeyer  wrote:
> Could this be
> https://github.com/cython/cython/issues/1375

Ah, I wasn't sure if that was a bug or a feature.  In an case, it can
easily be worked around from the Sage side.  Shall I open a ticket?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.rc1 released

[Erik Bray]

On Thu, Nov 16, 2017 at 2:51 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> e47ca9ea99 (tag: 8.1.rc1, trac/develop) Updated SageMath version to 8.1.rc1
> 1e26386030 Trac #24191: fpylll broken on Cygwin, again
> 652d8c6f6f Trac #22581: lack of service_identity Python package creates
> doctest failure
> b903855b4d Trac #24198: sage --notebook=export does not start
> 8f932e50ee Trac #24189: Python 2 libpython symlink not created correctly on
> Cygwin
> 307ceed91c Trac #24182: openssl security update (1.0.2m)
> 2e5b96f15c Trac #24190: Checking for overflow in matrix_mod2_dense not
> working on OS X 10.12.6
> 84eb9a5dfb Trac #23272: OpenBLAS - alterations for TARGET
> b707ce9348 (tag: 8.1.rc0) Updated SageMath version to 8.1.rc0


Doesn't build on Cygwin due to not having
https://trac.sagemath.org/ticket/24192 yet.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.1.rc2 released

[Erik Bray]

On Fri, Nov 17, 2017 at 2:29 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> 92f95cef93 (tag: 8.1.rc2) Updated SageMath version to 8.1.rc2
> 50a34e5f43 Trac #24192: -std=c99 causes numerous problems on Cygwin
> e47ca9ea99 (tag: 8.1.rc1) Updated SageMath version to 8.1.rc1

There is a new test failure on Cython (I think only with ptestlong)
that I somehow did not catch before:

sage -t src/sage/matrix/matrix_mod2_dense.pyx
**
File "src/sage/matrix/matrix_mod2_dense.pyx", line 183, in
sage.matrix.matrix_mod2_dense.Matrix_mod2_dense.__cinit__
Failed example:
if resource.RLIMIT_AS == resource.RLIMIT_RSS:
# Skip this test if RLIMIT_AS is not properly
# supported like on OS X, see Trac #24190
raise RuntimeError("matrix allocation failed")
else:  # Real test
MatrixSpace(GF(2), 2^30)(1)
Expected:
Traceback (most recent call last):
...
RuntimeError: matrix allocation failed
Got:

Traceback (most recent call last):
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 515, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 885, in compile_and_execute
exec(compiled, globs)
  File "", line
1, in 
if resource.RLIMIT_AS == resource.RLIMIT_RSS:
AttributeError: 'module' object has no attribute 'RLIMIT_RSS'
**
1 item had failures:
   1 of   8 in sage.matrix.matrix_mod2_dense.Matrix_mod2_dense.__cinit__
[337 tests, 1 failure, 3.32 s]
--
sage -t src/sage/matrix/matrix_mod2_dense.pyx  # 1 doctest failed
--

I'd like to get that fixed at the very least as it will fail all patchbots...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Sat, Dec 2, 2017 at 5:04 PM, Volker Braun  wrote:
> On Saturday, December 2, 2017 at 1:54:02 PM UTC+1, tsc...@ucdavis.edu wrote:
>>
>> What about https://trac.sagemath.org/ticket/24297? I don't know if this
>> problem materializes on other platforms, but I know Erik will be happy with
>> all tests passing on Cygwin. ;)
>
>
> Unfortunately, Eric's happiness will have to wait for 8.2.beta like all the
> other tickets ;-)

I don't see why.  What's the harm in merging a couple working branches?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Mon, Dec 4, 2017 at 3:16 PM, Jeroen Demeyer  wrote:
> On 2017-12-04 14:35, Erik Bray wrote:
>>
>> I don't see why.  What's the harm in merging a couple working branches?
>
>
> The first rc version of Sage 8.1 is now almost 1 month ago. We don't want to
> delay the release of 8.1 forever.

???

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Mon, Dec 4, 2017 at 10:49 PM, Nicolas M. Thiery
 wrote:
> On Sat, Dec 02, 2017 at 08:04:50AM -0800, Volker Braun wrote:
>> Unfortunately, Eric's happiness will have to wait for 8.2.beta like
>> all the other tickets ;-)
>
> It's not so much about Erik's happiness than good Cygwin support and
> therefore our Window's user happiness; a rather high priority in my
> view.
>
> Though I do care about Erik's happiness as well :-)
>
> And I also see the tension between release often and wait-until-ready
> schedules. At some point, we should have a discussion about what model
> we want for SageMath, and what prerequisites in terms of continuous
> integration this would take.

Plus the wait-until-ready did occur while waiting on the fix for
skylake.  In the meantime of that waiting the fixes I requested for
Windows were already sitting there waiting...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Tue, Dec 5, 2017 at 10:52 AM, Jeroen Demeyer  wrote:
> On 2017-12-04 19:18, Emmanuel Charpentier wrote:
>>
>> I already reported
>> 
>> (twice
>> 
>> !) that 8.1.rc(whatever) won't build without Trac#24121
>
>
> If you find that ticket so important, why didn't you change its priority to
> "blocker"? I see that this was done very recently, but if you had done that
> from the beginning, it would already have been merged.

I think directly e-mailing the release manager would also be "good
enough", but that was done and ignored *shrug*

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Tue, Dec 5, 2017 at 10:52 AM, Jeroen Demeyer  wrote:
> On 2017-12-04 19:18, Emmanuel Charpentier wrote:
>>
>> I already reported
>> 
>> (twice
>> 
>> !) that 8.1.rc(whatever) won't build without Trac#24121
>
>
> If you find that ticket so important, why didn't you change its priority to
> "blocker"? I see that this was done very recently, but if you had done that
> from the beginning, it would already have been merged.

Also it's less about "so important" is it is not about releasing
software with broken tests (even in minor ways).  The build procedure
for the binaries ensures that all the tests pass--obviously this can
be bypassed if really needed but that's basically cheating.  To that
end we should also add a buildbot for Cygwin if that's how Volker
determines whether or not a release is ready.  I will work on that
(I've only since come to understand that the 'patchbots' as opposed to
'buildbots' are merely advisory).

Furthermore I can't release "SageMath 8.1" if it's not the source
release tagged "8.1".  At best I can release SageMath 8.1-1 or
somesuch to indicate a patch level.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Tue, Dec 5, 2017 at 6:05 PM, Emmanuel Charpentier
 wrote:
>
>
> Le mardi 5 décembre 2017 10:52:14 UTC+1, Jeroen Demeyer a écrit :
>>
>> On 2017-12-04 19:18, Emmanuel Charpentier wrote:
>> > I already reported
>> > 
>> > (twice
>> > 
>> > !) that 8.1.rc(whatever) won't build without Trac#24121
>>
>> If you find that ticket so important, why didn't you change its priority
>> to "blocker"?
>
>
> 'cause I' a newbie : I am aware that I do not know many things about the
> development process : I report what I see or can achieve, and let people
> (presumably) more knowledgeable than I am take the "right" decisions. I do
> not want to make of myself a bigger pain in the @$$ than I am already :-).
>
>>
>> I see that this was done very recently, but if you had
>> done that from the beginning, it would already have been merged.
>
>
> Indeed. But I had some difficulty to convince others that a change breaking
> the last update to Windows 10 was importent enough : I thank that the
> critical fact is that Microsoft **pushes** this change to users. teling "do
> not upgrade now" is useless...

In fairness the one issue we're discussing here only affects building
Sage from source, and so as far as I'm concerned does not impact
"users", and the people building Sage from source on Windows can be
counted by a dog.  That said, as a matter of principal, it should have
been fixed, and I don't understand how the release manager chooses
which "positive_review" tickets are good enough to merge, and which
ones can be ignored.  The "priority" tag obviously has some influence
but when the default priority is "major" that still doesn't seem too
meaningful.  In my mind this was not a "blocker", but still important
to fix, and it has been available to merge for some time.

In retrospect I should have supplied a buildbot on Cygwin; though in
the case of this issue a buildbot might not have even caught it since,
as Emmanuel pointed out, it depends heavily on what Windows updates
are installed.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1.rc4 released

[Erik Bray]

On Tue, Dec 5, 2017 at 6:16 PM, Emmanuel Charpentier
 wrote:
>
>
> Le mardi 5 décembre 2017 18:03:19 UTC+1, Dima Pasechnik a écrit :
>>
>> The skylake wait was due to a bunch of active Sage users and devs needing
>> it and asking for it.
>>
>> Perhaps we should aim at 8.1.1 with Cygwin fix?
>
>
> The attention to Cygwin is indeed  justified by the hope of getting *new*
> Sage users (namely Windows 10 users).
> But I note that Trac#24121 has been positively reviewed for 4 weeks, whereas
> Trac#21233 has got positive review "only" 13 days ago.

It originally had "positive review" 5 months ago, then Volker set it
back to "needs work" due to a seemingly-related test that was failing.
In fact as far as I can tell that test was not directly related to my
fix, and was already broken due to a random nature of it, and it just
happened to fail (possibly my changes made it more likely to fail due
to entropy :).  I immediately corrected this and set it back to "needs
review", and then nothing...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.1 released

[Erik Bray]

On Mon, Dec 11, 2017 at 10:54 AM,   wrote:
> Volker, could you please get rid of the 66 "positive-reviewed as invalid"
> tickets ?
>
> Frédéric
>
> https://trac.sagemath.org/query?status=positive_review&milestone=sage-duplicate%2Finvalid%2Fwontfix&max=0&col=id&col=summary&col=owner&col=type&col=priority&col=milestone&col=component&order=id

I took care of it--in the past Volker has expressed not minding other
people doing it since he doesn't care.

> Le vendredi 8 décembre 2017 01:06:15 UTC+1, Volker Braun a écrit :
>>
>> The "master" git branch has been updated to Sage-8.1. As always, you can
>> get the latest beta version from the "develop" git branch. Alternatively,
>> the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> There was no change over 8.1rc4
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.2.beta0 released

[Erik Bray]

On Thu, Dec 14, 2017 at 11:36 AM, Dima Pasechnik  wrote:
>
>
> On Thursday, December 14, 2017 at 9:53:11 AM UTC, François Bissey wrote:
>>
>> I am sure I could get it directly from trac. It is just more convenient
>> from github when you started with a clone from the github repo.
>> And my live ebuilds also point to Github, I could point the one
>> that make sense to trac I guess.
>>
> At some point I proposed to have such a mirror as I am running now privately
> to be in
> https://github.com/sagemath organisation, but have not heard back from
> anyone...

That's something I'm hoping to work on but I'm already pretty overloaded.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.2.beta3 released

[Erik Bray]

On Thu, Jan 18, 2018 at 1:01 AM, Volker Braun  wrote:
> After reinstalling the OSX buildslave from scratch since the OSX 10.13
> upgrade resulted in a bootloop (why not let your customers beta-test the
> online migration to the new file system), we finally have a new release ;-)
>
>
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html

sage -t -a --long passing on Cygwin so long as I set timeout to zero,
otherwise some tests time out just due to being a bit slower in
general I guess.

I'll have to take a closer look sometime at which tests time out.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.beta3 released

[Erik Bray]

On Sun, Jan 21, 2018 at 11:48 AM, Emmanuel Charpentier
 wrote:
> On Cygwin64 running on Windows 7 (without admin rights) on the very same
> hardware as the previous report, a *serial* build of sage succeeds and
> passes testlong (*not* ptestlong) with one failure, which turns out to be
> consistent :
>
> --
> sage -t --long src/sage/interfaces/process.pyx  # 1 doctest failed
> --
>
> The failing test checks that a process terminates in less than 4 seconds. On
> this hardware and OS, it takes consistently about 4.5 seconds to terminate a
> process...
>
> Notwithstanding this booboo, this means that a self-compiled Sage can be
> considered as reliable as a Unix version on this platform. Kudos to Erik M.
> Bray !
>
> One should also note that the time necessary to pass testlong is about
> twiice what could be expected by extrapolating from a Linux ptestlong on the
> same hardware (IIRC (no hard data on hand), ptestkong with MAKE="make -j4"
> on this machines takes a bit less than 2 hours) :
>
> Total time for all tests: 56735.9 seconds
> cpu time: 16037.3 seconds
> cumulative wall time: 41802.8 seconds
> make: *** [Makefile:101: testlong] Error 1
>
> real958m8,294s
> user616m4,845s
> sys 223m47,946s
>


On my system it's quite a bit faster:

Total time for all tests: 10755.9 seconds
cpu time: 15559.3 seconds
cumulative wall time: 19960.9 seconds

And that's only with 2 processes.  I could go up to 8 if I stopped
using my system for anything else :)  What I really need now is better
hardware for the patchbot.

> Finally, I recall that I have been unable to build or test in parallel with
> Cygwin. That should nod be a problem per se, but leads to questions about
> using parallelism on this platform.

I'm still not sure what problem you're having here.  Works fine for
me.  Parallel build *sometimes* has random failures, which I think are
related to rebasing.  It may actually be a problem for one make job to
be writing/installing to SAGE_LOCAL while another is running
sage-rebase.  Multi-stage install as in
https://trac.sagemath.org/ticket/24106 may help alleviate that.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.2.beta4 released

[Erik Bray]

On Sun, Jan 28, 2018 at 8:17 AM, Ralf Stephan  wrote:
> This is https://trac.sagemath.org/ticket/24599
> I'm trying now with the system gcc.

I don't have this problem on Ubuntu but I am getting:

[giac-1.4.9.45] libtool: link: g++ -g -O2 -fno-strict-aliasing
-DGIAC_GENERIC_CONSTANTS -Wl,-rpath
-Wl,/home/embray/src/sagemath/sage/local/lib -o .libs/icas icas.o
-L/home/embray/src/sagemath/sage/local/lib ./.libs/libxcas.a
/home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so
-lntl -lpari -lreadline -lgsl -lgslcblas -lrt -lpthread -lglpk -ldl
-lpng -lm -lmpfi /home/embray/src/sagemath/sage/local/lib/libmpfr.so
-lgmp -Wl,-rpath -Wl,/home/embray/src/sagemath/sage/local/lib
[giac-1.4.9.45]
/home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so:
undefined reference to `png_set_longjmp_fn'
[giac-1.4.9.45] collect2: error: ld returned 1 exit status


So this has rendered this beta unbuildable for me.


> On Sun, Jan 28, 2018 at 8:09 AM François Bissey 
> wrote:
>>
>> I was going to warn sage-on-gentoo users on this interesting fact that I
>> experienced
>> on the experimental branch where I track stuff that Volker merges.
>> It is probably an issue in giac, but at the end of the day gcc needs to be
>> rebuilt
>> after mpfr/mpc. I didn’t think about the problem of what happens when you
>> use
>> the host gcc in vanilla sage though.
>> You may have to build sage’s gcc - or use clang once support is merged :)
>>
>> François
>>
>> > On 28/01/2018, at 20:02, Ralf Stephan  wrote:
>> >
>> > Compiling giac with the gcc installed by Sage (7.2.0) gives an internal
>> > compiler error:
>> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>> > -I.. -I/h
>> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>> > -I/home/ralf/
>> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>> > solve.lo -M
>> > D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
>> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>> > -I.. -I/h
>> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>> > -I/home/ralf/
>> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>> > derive.lo -
>> > MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
>> > init2.c:52: MPFR assertion failed: p >= 2 && p <=
>> > ((mpfr_prec_t)((mpfr_uprec_t)(
>> > ~(mpfr_uprec_t)0)>>1))
>> > modpoly.cc: In function 'std::complex giac::horner_newton(const
>> > vecteur&
>> > , const std::complex&, const giac::context*)':
>> > modpoly.cc:5035:19: internal compiler error: Aborted
>> >complex horner_newton(const vecteur & p,const
>> > std::complex &x
>> > ,GIAC_CONTEXT){
>> >^
>> > 0xafbc6f crash_signal
>> > ../../src/gcc/toplev.c:337
>> > 0x7f3e0cfeedd3 mpfr_assert_fail
>> >
>> > /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
>> > c:305
>> > 0x7f3e0cfe59c1 mpfr_init2
>> >
>> > /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
>> > 2
>> > 0x7f3e0d21b472 mpc_div_zero
>> >
>> > /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
>> > 0x7f3e0d21b472 mpc_div
>> >
>> > /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
>> > 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int
>> > (*)(__mpc_stru
>> > ct*, __mpc_struct const*, __mpc_struct const*, int))
>> > ../../src/gcc/builtins.c:10179
>> > 0x8afa0a const_binop
>> > ../../src/gcc/fold-const.c:1316
>> > 0x8b0c5e const_binop(tree_code, tree_node*, tree_node*, tree_node*)
>> > ../../src/gcc/fold-const.c:1565
>> > 0xdb4962 gimple_resimplify2(gimple**, code_helper*, tree_node*,
>> > tree_node**, tre
>> > e_node* (*)(tree_node*))
>> > ../../src/gcc/gimple-match-head.c:132
>> > 0xe384b0 gimple_simplify(gimple*, code_helper*, tree_node**, gimple**,
>> > tree_node
>> > * (*)(tree_node*), tree_node* (*)(tree_node*))
>> > ../../src/gcc/gimple-match-head.c:642
>> > 0x8e4306 fold_stmt_1
>> > ../../src/gcc/gimple-fold.c:4362
>> > 0xbdb5ff execute
>> > ../../src/gcc/tree-ssa-forwprop.c:2391
>> > Please submit a full bug report,
>> > with preprocessed source if appropriate
>> >
>> > The complete log is attached. System is OpenSuSE 42.3.
>> >
>> > On Sun, Jan 28, 2018 at 1:08 AM Volker Braun 
>> > wrote:
>> > As always, you can get the latest beta version from the "develop" git
>> > branch. Alternatively, the self-contained source tarball is at
>> > http://www.sagemath.org/download-latest.html
>> >
>> > 0a674fd488 (tag: 8.2.beta4, trac/develop) Updated SageMath version to
>> > 8.2.beta4
>> > 4d966299d9 Trac #24581: more typos
>> > 59b6f2aff8 Trac #24580: some typos (various)
>> > 3e3b72af47 Trac #24592: "./sage -f" should clean first before building
>> > the toolchain
>> > e486b8d5b7 Trac #24586: packages whose type is "script" must h

Re: [sage-release] Sage 8.2.beta4 released

[Erik Bray]

On Tue, Jan 30, 2018 at 7:05 PM, François Bissey  wrote:
> David Coudert got that (on sage-devel I think). Turns out the libpng
> install was broken for some reason and was missing libpng.so.
> ./sage -f libpng
> solves this. But you are the second person reporting this which
> makes it suspicious. Is something out there deleting libpng.so?

I just did a full `make distclean && make build` and that seemed to
fix it as well.  I didn't try `./sage -f libpng` but I should
have--that might have been faster :)

I'll look into it.

Thanks,
E

>> On 31/01/2018, at 01:34, Erik Bray  wrote:
>>
>> On Sun, Jan 28, 2018 at 8:17 AM, Ralf Stephan  wrote:
>>> This is https://trac.sagemath.org/ticket/24599
>>> I'm trying now with the system gcc.
>>
>> I don't have this problem on Ubuntu but I am getting:
>>
>> [giac-1.4.9.45] libtool: link: g++ -g -O2 -fno-strict-aliasing
>> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath
>> -Wl,/home/embray/src/sagemath/sage/local/lib -o .libs/icas icas.o
>> -L/home/embray/src/sagemath/sage/local/lib ./.libs/libxcas.a
>> /home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so
>> -lntl -lpari -lreadline -lgsl -lgslcblas -lrt -lpthread -lglpk -ldl
>> -lpng -lm -lmpfi /home/embray/src/sagemath/sage/local/lib/libmpfr.so
>> -lgmp -Wl,-rpath -Wl,/home/embray/src/sagemath/sage/local/lib
>> [giac-1.4.9.45]
>> /home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so:
>> undefined reference to `png_set_longjmp_fn'
>> [giac-1.4.9.45] collect2: error: ld returned 1 exit status
>>
>>
>> So this has rendered this beta unbuildable for me.
>>
>>
>>> On Sun, Jan 28, 2018 at 8:09 AM François Bissey 
>>> wrote:
>>>>
>>>> I was going to warn sage-on-gentoo users on this interesting fact that I
>>>> experienced
>>>> on the experimental branch where I track stuff that Volker merges.
>>>> It is probably an issue in giac, but at the end of the day gcc needs to be
>>>> rebuilt
>>>> after mpfr/mpc. I didn’t think about the problem of what happens when you
>>>> use
>>>> the host gcc in vanilla sage though.
>>>> You may have to build sage’s gcc - or use clang once support is merged :)
>>>>
>>>> François
>>>>
>>>>> On 28/01/2018, at 20:02, Ralf Stephan  wrote:
>>>>>
>>>>> Compiling giac with the gcc installed by Sage (7.2.0) gives an internal
>>>>> compiler error:
>>>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>>>>> -I.. -I/h
>>>>> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>>>>> -I/home/ralf/
>>>>> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>>>>> solve.lo -M
>>>>> D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
>>>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>>>>> -I.. -I/h
>>>>> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>>>>> -I/home/ralf/
>>>>> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>>>>> derive.lo -
>>>>> MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
>>>>> init2.c:52: MPFR assertion failed: p >= 2 && p <=
>>>>> ((mpfr_prec_t)((mpfr_uprec_t)(
>>>>> ~(mpfr_uprec_t)0)>>1))
>>>>> modpoly.cc: In function 'std::complex giac::horner_newton(const
>>>>> vecteur&
>>>>> , const std::complex&, const giac::context*)':
>>>>> modpoly.cc:5035:19: internal compiler error: Aborted
>>>>>   complex horner_newton(const vecteur & p,const
>>>>> std::complex &x
>>>>> ,GIAC_CONTEXT){
>>>>>   ^
>>>>> 0xafbc6f crash_signal
>>>>>../../src/gcc/toplev.c:337
>>>>> 0x7f3e0cfeedd3 mpfr_assert_fail
>>>>>
>>>>> /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
>>>>> c:305
>>>>> 0x7f3e0cfe59c1 mpfr_init2
>>>>>
>>>>> /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
>>>>> 2
>>>>> 0x7f3e0d21b472 mpc_div_zero
>>>>>
>>>>> /home/ralf/sage/local/var/tmp/sag

Re: [sage-release] Sage 8.2.beta4 released

[Erik Bray]

On Wed, Jan 31, 2018 at 3:02 PM, Erik Bray  wrote:
> On Tue, Jan 30, 2018 at 7:05 PM, François Bissey  wrote:
>> David Coudert got that (on sage-devel I think). Turns out the libpng
>> install was broken for some reason and was missing libpng.so.
>> ./sage -f libpng
>> solves this. But you are the second person reporting this which
>> makes it suspicious. Is something out there deleting libpng.so?
>
> I just did a full `make distclean && make build` and that seemed to
> fix it as well.  I didn't try `./sage -f libpng` but I should
> have--that might have been faster :)
>
> I'll look into it.

So there's this long note in the SPKG.txt for libpng about:

"On Darwin, the symbolic links libpng.* created by libpng16 may
interfere with a system-wide libPng.dylib."
Which on the face of it sounds fishy to me.  That was added,
apparently, way back in 2008, and to me suggests some kind of
misconfiguration more than anything.

That said, another strange thing about this is that on my Windows
patchbot where I first saw this problem, those symlinks it's supposed
to delete are still there, even though the the spkg-install very
clearly says "rm -f $SAGE_LOCAL/lib/libpng.*"  I don't see anything
that would have put those links back either...

Furthermore, I can clearly see that giac is trying to link with -lpng
and not -lpng16.  Following the discussion in libpng/SPKG.txt, it
should really be using -lpng16, which is *probably* why it didn't work
for me the first time around.

But now I don't understand why the `rm -f ...` didn't work.  Perhaps a
shell setting of some kind involving expanding symlinks in globs?

Best,
E



>>> On 31/01/2018, at 01:34, Erik Bray  wrote:
>>>
>>> On Sun, Jan 28, 2018 at 8:17 AM, Ralf Stephan  wrote:
>>>> This is https://trac.sagemath.org/ticket/24599
>>>> I'm trying now with the system gcc.
>>>
>>> I don't have this problem on Ubuntu but I am getting:
>>>
>>> [giac-1.4.9.45] libtool: link: g++ -g -O2 -fno-strict-aliasing
>>> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath
>>> -Wl,/home/embray/src/sagemath/sage/local/lib -o .libs/icas icas.o
>>> -L/home/embray/src/sagemath/sage/local/lib ./.libs/libxcas.a
>>> /home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so
>>> -lntl -lpari -lreadline -lgsl -lgslcblas -lrt -lpthread -lglpk -ldl
>>> -lpng -lm -lmpfi /home/embray/src/sagemath/sage/local/lib/libmpfr.so
>>> -lgmp -Wl,-rpath -Wl,/home/embray/src/sagemath/sage/local/lib
>>> [giac-1.4.9.45]
>>> /home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so:
>>> undefined reference to `png_set_longjmp_fn'
>>> [giac-1.4.9.45] collect2: error: ld returned 1 exit status
>>>
>>>
>>> So this has rendered this beta unbuildable for me.
>>>
>>>
>>>> On Sun, Jan 28, 2018 at 8:09 AM François Bissey 
>>>> wrote:
>>>>>
>>>>> I was going to warn sage-on-gentoo users on this interesting fact that I
>>>>> experienced
>>>>> on the experimental branch where I track stuff that Volker merges.
>>>>> It is probably an issue in giac, but at the end of the day gcc needs to be
>>>>> rebuilt
>>>>> after mpfr/mpc. I didn’t think about the problem of what happens when you
>>>>> use
>>>>> the host gcc in vanilla sage though.
>>>>> You may have to build sage’s gcc - or use clang once support is merged :)
>>>>>
>>>>> François
>>>>>
>>>>>> On 28/01/2018, at 20:02, Ralf Stephan  wrote:
>>>>>>
>>>>>> Compiling giac with the gcc installed by Sage (7.2.0) gives an internal
>>>>>> compiler error:
>>>>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>>>>>> -I.. -I/h
>>>>>> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>>>>>> -I/home/ralf/
>>>>>> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>>>>>> solve.lo -M
>>>>>> D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
>>>>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>>>>>> -I.. -I/h
>>>>>> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>>>>>> -I/home/ralf/
>>>>>> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>

Re: [sage-release] Re: Sage 8.2.beta6 released

[Erik Bray]

On Mon, Feb 19, 2018 at 2:31 PM, Emmanuel Charpentier
 wrote:
> On Debian testing running on core i5 + 8 GB RAM, 8.2.beta6 builds and passes
> ptestlong with one (permanent) failure related to fricas (optional package)
> :
>
> charpent@p-202-021:/usr/local/sage-8$ sage -t --long --warn-long 52.1
> src/sage/interfaces/fricas.py
> Running doctests with ID 2018-02-19-14-18-38-dc60aa34.
> Git branch: develop
> Using
> --optional=database_gap,dot2tex,fricas,giacpy_sage,mpir,pandocfilters,python2,sage
> Doctesting 1 file.
> sage -t --long --warn-long 52.1 src/sage/interfaces/fricas.py
> **
> File "src/sage/interfaces/fricas.py", line 1096, in
> sage.interfaces.fricas.FriCASElement._sage_expression
> Failed example:
> [f(x)._fricas_().sage().subs(x=0.9) for f in l]   # optional
> - fricas
> Expected:
> [0.716297870199024,
>  1.02651672570818,
>  1.43308638544877,
>  1.39606725303001,
>  0.697794641100332,
>  0.974168247780004,
>  0.808866935652782,
>  0.451026811796262*I,
>  1.47221948958322,
>  1.47221948958322,
>  0.467145308103262,
>  0.957800449200672,
>  0.808866935652782,
>  0.451026811796262*I,
>  1.47221948958322,
>  1.47221948958322,
>  0.467145308103262,
>  0.957800449200672]
> Got:
> [0.716297870199024,
>  1.02651672570818,
>  1.43308638544877,
>  1.39606725303001,
>  0.697794641100332,
>  0.974168247780004,
>  0.808866935652782,
>  0.451026811796262*I,
>  1.47221948958322,
>  1.47221948958322 - 1.57079632679490*I,
>  0.467145308103262,
>  0.957800449200672,
>  0.808866935652782,
>  0.451026811796262*I,
>  1.47221948958322,
>  1.47221948958322 - 1.57079632679490*I,
>  0.467145308103262,
>  0.957800449200672]
> **
> 1 item had failures:
>1 of  10 in sage.interfaces.fricas.FriCASElement._sage_expression
> [173 tests, 1 failure, 27.67 s]
> --
> sage -t --long --warn-long 52.1 src/sage/interfaces/fricas.py  # 1 doctest
> failed
> --
> Total time for all tests: 32.8 seconds
> cpu time: 2.0 seconds
> cumulative wall time: 27.7 seconds
>
> This doesn't seems to be numerical noise _proprio dictu_, but this addition
> of a -I*pi term might be _related to_ numerical noise.
>
> Ticket-worthy ?

I've seen the same failure before in the fricas tests, so it's not new
at least.   I just haven't bothered about it because I don't know how
much we care about supporting optional packages...


> Le dimanche 18 février 2018 21:09:15 UTC+1, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> 93020a4eb1 (tag: 8.2.beta6, trac/develop) Updated SageMath version to
>> 8.2.beta6
>> c66161549b Trac #24727: Graphs, check for algorithm
>> 055b6b0f3f Trac #24743: more use of https links for wikipedia links
>> ed5c8ea165 Trac #24736: py3: adding some # py2 tags about range in rst
>> files
>> 36995e8285 Trac #24734: use the pep role in more places
>> e15d48ad51 Trac #24725: Make power poset a meet-semilattice
>> aa03e3be74 Trac #23977: QuadraticForm doubling convention inconsistent
>> 4c905b7614 Trac #24739: Open lazy_import cache file in binary mode
>> 5681df2c13 Trac #24738: Rename _coerce_c_impl method in
>> BooleanPolynomialRing
>> 2e30908c1c Trac #24733: Graph.is_asteroidal_triple_free not usable as
>> method
>> 4f555346f7 Trac #24732: use https in standard license header
>> 8445e099fc Trac #24731: use https in new deprecation links
>> 11692a1bbe Trac #24722: Minor cleanup in sage.misc.cython
>> d47ad44fd1 Trac #24721: upgrade sqlite to 3.22
>> 8c5115bd62 Trac #24704: ppl build fails with clang-5.0
>> f44358946f Trac #24745: leaking in the symbolic ring
>> 68d39754c2 Trac #24667: Clean up partitions_c.cc
>> c273e63a1f Trac #24568: Deprecate sage.rings.real_mpfr.RealNumber.__hex__
>> 77bcb4712c Trac #24507: py3: minor fixes to sage.libs.pynac
>> 4863f46236 Trac #24414: py3: sage.libs.singular fixes
>> 169ae42529 Trac #24256: Deprecate sage.structure.element.generic_power
>> 16ac02c873 Trac #24059: py3 : add some decode in jmoldata and tachyon
>> interfaces
>> 40295d60b4 Trac #23177: Upgrade to ipywidgets-7
>> d7195f1f35 Trac #24698: fixing one plantri doctest
>> 26ac65cf67 Trac #24723: Add a note about N-free posets
>> 42733ab338 Trac #24683: fix various issues in for weighted Hamiltonian
>> path.
>> 8623cf0455 Trac #24719: fix wrong import of gamma
>> 7cb711395a Trac #24713: Upgrade cypari2
>> 411acce6b9 Trac #24649: Clean up and documentation improvements with
>> hyperbolic functions
>> 8a64691e82 Trac #24371: Move real/comple

Re: [sage-release] Sage 8.2.beta6 released

[Erik Bray]

Looks good on Cygwin--some tests failed due to timeout (not uncommon)
but passed when run again with --failed, so I'm not too concerned
about that.  Some tests, in particular those that run lots of
subprocess (such as sage.tests.cmdline) frequently take a bit longer
on Cygwin, especially when run in parallel.

On Sun, Feb 18, 2018 at 9:09 PM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> 93020a4eb1 (tag: 8.2.beta6, trac/develop) Updated SageMath version to
> 8.2.beta6
> c66161549b Trac #24727: Graphs, check for algorithm
> 055b6b0f3f Trac #24743: more use of https links for wikipedia links
> ed5c8ea165 Trac #24736: py3: adding some # py2 tags about range in rst files
> 36995e8285 Trac #24734: use the pep role in more places
> e15d48ad51 Trac #24725: Make power poset a meet-semilattice
> aa03e3be74 Trac #23977: QuadraticForm doubling convention inconsistent
> 4c905b7614 Trac #24739: Open lazy_import cache file in binary mode
> 5681df2c13 Trac #24738: Rename _coerce_c_impl method in
> BooleanPolynomialRing
> 2e30908c1c Trac #24733: Graph.is_asteroidal_triple_free not usable as method
> 4f555346f7 Trac #24732: use https in standard license header
> 8445e099fc Trac #24731: use https in new deprecation links
> 11692a1bbe Trac #24722: Minor cleanup in sage.misc.cython
> d47ad44fd1 Trac #24721: upgrade sqlite to 3.22
> 8c5115bd62 Trac #24704: ppl build fails with clang-5.0
> f44358946f Trac #24745: leaking in the symbolic ring
> 68d39754c2 Trac #24667: Clean up partitions_c.cc
> c273e63a1f Trac #24568: Deprecate sage.rings.real_mpfr.RealNumber.__hex__
> 77bcb4712c Trac #24507: py3: minor fixes to sage.libs.pynac
> 4863f46236 Trac #24414: py3: sage.libs.singular fixes
> 169ae42529 Trac #24256: Deprecate sage.structure.element.generic_power
> 16ac02c873 Trac #24059: py3 : add some decode in jmoldata and tachyon
> interfaces
> 40295d60b4 Trac #23177: Upgrade to ipywidgets-7
> d7195f1f35 Trac #24698: fixing one plantri doctest
> 26ac65cf67 Trac #24723: Add a note about N-free posets
> 42733ab338 Trac #24683: fix various issues in for weighted Hamiltonian path.
> 8623cf0455 Trac #24719: fix wrong import of gamma
> 7cb711395a Trac #24713: Upgrade cypari2
> 411acce6b9 Trac #24649: Clean up and documentation improvements with
> hyperbolic functions
> 8a64691e82 Trac #24371: Move real/complex interval fields to new coercion
> model
> ee52455663 Trac #24286: py3: minor fixes to sage.repl.load and
> sage.repl.attach
> 5acceec251 Trac #24665: Implement rational_torsion_order for modular abelian
> varieties
> 0fad24c606 Trac #24709: Random failure in RealField_class._coerce_map_from_
> 4080b731ac Trac #24668: Upgrade to pynac-0.7.16
> 9b841e1b68 Trac #24696: giac fails to compile with clang-3.8 on OpenSuSE
> ee83f2abc5 Trac #24694: gfortran should not be installed if the gcc package
> is installed
> 02476b22d3 Trac #24684: more on interval-posets
> e72e693421 Trac #24673: Add a method to clear coercion caches of a parent
> 609a04de04 Trac #24693: Fixes for Cython 0.28
> 45cdd651eb Trac #24663: Posets: Add is_greedy()
> 9ae3615190 Trac #24697: Upgrade MPFR to 4.0.1
> fccaf230e8 Trac #24690: Install Cython source files
> 98ea3bcf08 Trac #24695: Fix ComplexIntervalFieldElement.log()
> 9254fd6b91 Trac #24687: Fix wrong peirce_summand
> f8063012e2 Trac #24679: Fix factor() for non-Sage numbers
> d2ddad65ad Trac #24521: Abelian Groups with Gap
> 06959420e2 Trac #23362: Upgrade to pandocfilters 1.4.2
> 52ab1fbec1 Trac #24666: Use return instead of raising StopIteration
> 76d8def267 Trac #24664: Implement Artin groups for finite type
> 08a66bf04d Trac #24653: Implement _unicode_art_ for crystals
> b480d15710 Trac #24652: UnicodeArt is unable to convert to a unicode object
> 577f606622 Trac #24651: Disable pexpect echo when starting the interface
> cb7551 Trac #24643: Fix linking of Flint on FreeBSD and other platforms
> 870d1d87cd Trac #24640: Avoid order computation in EllipticCurveIsogeny
> function
> a6df142fd9 Trac #24621: Fix conversions to CBF
> 9cf1756be5 Trac #24423: LinearFunctionOrConstraint.__richcmp__ should
> replace before converting
> 66f944cbd3 Trac #24369: upgrade arb to 2.12.0
> f373c6fd37 Trac #21869: A framework for discrete valuations in Sage
> 4e8ebfdba3 Trac #24670: Doctest framework fixes for matplotlib
> 219b1b6eb6 Trac #24650: Fix subprocess32 build on Solaris and Python 3
> 03c2294c4d Trac #24567: Python bugs with tarfile structure and permissions
> e6cae6d88d (tag: 8.2.beta5) Updated SageMath version to 8.2.beta5
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https:

Re: [sage-release] Re: Sage 8.2.beta7 released

[Erik Bray]

On Fri, Mar 9, 2018 at 9:53 AM, Emmanuel Charpentier
 wrote:
> FWIW, (serially) builds successfully on Cygwin64 running on top of Windows 7
> (on Core i5 + 8 GB RAM), but only after applying Trac#24860. Serial build
> needs about 15 hours. Tests will have to be run overnight.

Why "serial".  Parallel build works fine most of the time, modulo the
issues discussed (and fixed) in https://trac.sagemath.org/ticket/24647


> Le mardi 6 mars 2018 10:45:59 UTC+1, Emmanuel Charpentier a écrit :
>>
>> FWIW, same result onDeian testing running on Core i5 + 8 GB RAM.
>>
>> --
>> Emmanuel Charpentier
>>
>> Le samedi 3 mars 2018 12:09:52 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> FWIW, builds and passes ptestlong without any failure on Debian testing
>>> running on Core i7 + 16 GB RAM
>>>
>>> HTH,
>>>
>>> --
>>> Emmanuel Charpentier
>>>
>>> Le samedi 3 mars 2018 01:50:39 UTC+1, Volker Braun a écrit :

 As always, you can get the latest beta version from the "develop" git
 branch. Alternatively, the self-contained source tarball is at
 http://www.sagemath.org/download-latest.html

 3750eaa411 (tag: 8.2.beta7) Updated SageMath version to 8.2.beta7
 c6fc4193d4 Trac #24703: Everything should be rebuilt after GCC upgrade
 2e2a69c75c Trac #24772: Encoding fixes to the doctest module
 6e3e9d6c11 Trac #24813: py3: Miscellaneous small fixes for sage.arith
 a990a92f51 Trac #24810: _mul_ for IntegralLattices
 3796ed7999 Trac #24831: py3: remove __cmp__ in categories/functor
 87d791e0aa Trac #24829: zero_matrix() should pass the correct zero
 9734864877 Trac #24818: Bug in genus of a quadratic form
 7c12eda717 Trac #24814: Don't abuse prepare_dict() in ChainComplex
 11ba8c5297 Trac #24773: Delayed/Conditional Substitution
 d906dc42d8 Trac #24588: py3: several long/int related fixes
 5442f6226d Trac #24827: Doctest failures in fricas interface
 c191117f78 Trac #24635: make vertex_connectivity faster if only a lower
 bound is required.
 f1e208372b Trac #24799: Raising NotImplemented
 deaa572ec5 Trac #24803: fixing some bad use of raise
 8e985ebea4 Trac #24789: py3: updates to sage.interfaces.qsieve
 58bc11397d Trac #24573: bug in creating graphic matroid with explicit
 groundset labels
 196d3cc383 Trac #24391: DynkinDiagram.marked_nodes doesn't work
 b0d74897a9 Trac #19628: lazy_import breaks CachedRepresentation
 7640d68cb6 Trac #24702: Intersections and saturations of
 FreeQuadraticModules have the wrong ambient module
 76ae35b3b1 Trac #24787: Fix indentation in sage.misc.randstate
 0fb74a8f7e Trac #24794: py3: remove some commented __cmp__ (for cleanup)
 a77a2f0bd8 Trac #24781: another branch of typos
 d61e7dedd5 Trac #24777: Chromatic number of the empty graph by MILP
 884072c50c Trac #24796: py3: sort repr of OrlikSolomonAlgebra
 44c25dc927 Trac #24795: py3: fix pickling of
 sage.symbolic.function.SymbolicFunction
 6c18344f3e Trac #24720: Totally silent mode for cython()
 e67f4fbd16 Trac #23701: new standard package libatomic_ops
 88dc0cfa59 Trac #24780: py3: convert a few more classes to new-style
 classes
 186207a5d8 Trac #24778: py3: fix some minor doctest failures in
 sage.libs.mpmath
 6ad7c8a7e2 Trac #24759: Sort the repr of PolyDict by its dict keys
 f75e7b6bc8 Trac #24771: Miscellaneous fixes to the doctest module
 e32b57a4c5 Trac #24770: Doctest: use new-style classes
 3d5cc7aed2 Trac #24729: Add --with-python=3 configure flag to replace
 SAGE_PYTHON3=yes
 ba0d124149 Trac #24724: Capture warning/errors messages in
 sage.misc.cython
 d87395f04c Trac #24686: Integration of piecewise analytic complex
 functions using arb
 c8015d7a71 Trac #24531: Replace ratpoints by PARI
 50a97b3777 Trac #24763: Run scripts with sage-python23
 43a39f6c1b Trac #24744: implementation of boomerang connectivity table
 93020a4eb1 (tag: 8.2.beta6) Updated SageMath version to 8.2.beta6

> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.beta8 released

[Erik Bray]

I am now pretty consistently getting the following failure on Cygwin
with 8.2beta8 (although strangely I've run the test once or twice with
success too...):

sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx
**
File "src/sage/structure/coerce_actions.pyx", line 786, in
sage.structure.coerce_actions.IntegerMulAction._repr_name_
Failed example:
IntegerMulAction(ZZ, GF5)
Expected:
Left Integer Multiplication by Integer Ring on Finite Field of size 5
Got:
Left Integer Multiplication by Integer Ring on Finite Field of size 1
**
1 item had failures:
   1 of   4 in sage.structure.coerce_actions.IntegerMulAction._repr_name_
[143 tests, 1 failure, 3.30 s]
--
sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx  # 1
doctest failed

bizarre. Maybe some kind of cache bug?

On Wed, Mar 14, 2018 at 4:34 PM, Sébastien Labbé  wrote:
> On Ubuntu 16.04, my first attempt at running make finishes with a problem
> with giac (undefined reference to `png_set_longjmp_fn')
>
> The log finishes with:
>
> ...
> [giac-1.4.9.45.p2] libtool: link: g++ -g -O2 -fno-strict-aliasing
> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib
> -o .libs/icas icas.o  -L/home/slabbe/GitBox/sage/local/lib ./.libs/libxcas.a
> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so
> -lntl -lpari -lreadline -ltermcap -lgsl -lgslcblas -lrt -lpthread -lglpk
> -ldl -lpng -lm -lmpfi /home/slabbe/GitBox/sage/local/lib/libmpfr.so -lgmp
> -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib
> [giac-1.4.9.45.p2]
> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so:
> undefined reference to `png_set_longjmp_fn'
> [giac-1.4.9.45.p2] collect2: error: ld returned 1 exit status
> [giac-1.4.9.45.p2] Makefile:579: recipe for target 'icas' failed
> [giac-1.4.9.45.p2] make[5]: *** [icas] Error 1
> [giac-1.4.9.45.p2] make[5]: Leaving directory
> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src'
> [giac-1.4.9.45.p2] Makefile:404: recipe for target 'all-recursive' failed
> [giac-1.4.9.45.p2] make[4]: *** [all-recursive] Error 1
> [giac-1.4.9.45.p2] make[4]: Leaving directory
> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
> [giac-1.4.9.45.p2] Makefile:333: recipe for target 'all' failed
> [giac-1.4.9.45.p2] make[3]: *** [all] Error 2
> [giac-1.4.9.45.p2] make[3]: Leaving directory
> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
> [giac-1.4.9.45.p2]
> 
> [giac-1.4.9.45.p2] Error building giac-1.4.9.45.p2
> [giac-1.4.9.45.p2]
> 
> ...
>
> I did
>
> sage -f libpng && make
>
> which seems to have fixed the error:
>
> ...
> [giac-1.4.9.45.p2] successfully installed.
> ...
>
> ... still running.
>
> Sébastien
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.beta8 released

[Erik Bray]

On Wed, Mar 14, 2018 at 4:49 PM, Erik Bray  wrote:
> I am now pretty consistently getting the following failure on Cygwin
> with 8.2beta8 (although strangely I've run the test once or twice with
> success too...):
>
> sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx
> **
> File "src/sage/structure/coerce_actions.pyx", line 786, in
> sage.structure.coerce_actions.IntegerMulAction._repr_name_
> Failed example:
> IntegerMulAction(ZZ, GF5)
> Expected:
> Left Integer Multiplication by Integer Ring on Finite Field of size 5
> Got:
> Left Integer Multiplication by Integer Ring on Finite Field of size 1
> **
> 1 item had failures:
>1 of   4 in sage.structure.coerce_actions.IntegerMulAction._repr_name_
> [143 tests, 1 failure, 3.30 s]
> --
> sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx  # 1
> doctest failed
>
> bizarre. Maybe some kind of cache bug?

Well, I've been trying to debug this for a last hour and it got pretty
deep pretty fast.  I'm looking now at the possibility of a memory
allocation bug in MPIR/GMP...


> On Wed, Mar 14, 2018 at 4:34 PM, Sébastien Labbé  wrote:
>> On Ubuntu 16.04, my first attempt at running make finishes with a problem
>> with giac (undefined reference to `png_set_longjmp_fn')
>>
>> The log finishes with:
>>
>> ...
>> [giac-1.4.9.45.p2] libtool: link: g++ -g -O2 -fno-strict-aliasing
>> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib
>> -o .libs/icas icas.o  -L/home/slabbe/GitBox/sage/local/lib ./.libs/libxcas.a
>> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so
>> -lntl -lpari -lreadline -ltermcap -lgsl -lgslcblas -lrt -lpthread -lglpk
>> -ldl -lpng -lm -lmpfi /home/slabbe/GitBox/sage/local/lib/libmpfr.so -lgmp
>> -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib
>> [giac-1.4.9.45.p2]
>> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so:
>> undefined reference to `png_set_longjmp_fn'
>> [giac-1.4.9.45.p2] collect2: error: ld returned 1 exit status
>> [giac-1.4.9.45.p2] Makefile:579: recipe for target 'icas' failed
>> [giac-1.4.9.45.p2] make[5]: *** [icas] Error 1
>> [giac-1.4.9.45.p2] make[5]: Leaving directory
>> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src'
>> [giac-1.4.9.45.p2] Makefile:404: recipe for target 'all-recursive' failed
>> [giac-1.4.9.45.p2] make[4]: *** [all-recursive] Error 1
>> [giac-1.4.9.45.p2] make[4]: Leaving directory
>> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
>> [giac-1.4.9.45.p2] Makefile:333: recipe for target 'all' failed
>> [giac-1.4.9.45.p2] make[3]: *** [all] Error 2
>> [giac-1.4.9.45.p2] make[3]: Leaving directory
>> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
>> [giac-1.4.9.45.p2]
>> 
>> [giac-1.4.9.45.p2] Error building giac-1.4.9.45.p2
>> [giac-1.4.9.45.p2]
>> 
>> ...
>>
>> I did
>>
>> sage -f libpng && make
>>
>> which seems to have fixed the error:
>>
>> ...
>> [giac-1.4.9.45.p2] successfully installed.
>> ...
>>
>> ... still running.
>>
>> Sébastien
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.beta8 released

[Erik Bray]

On Wed, Mar 14, 2018 at 6:41 PM, Erik Bray  wrote:
> On Wed, Mar 14, 2018 at 4:49 PM, Erik Bray  wrote:
>> I am now pretty consistently getting the following failure on Cygwin
>> with 8.2beta8 (although strangely I've run the test once or twice with
>> success too...):
>>
>> sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx
>> **
>> File "src/sage/structure/coerce_actions.pyx", line 786, in
>> sage.structure.coerce_actions.IntegerMulAction._repr_name_
>> Failed example:
>> IntegerMulAction(ZZ, GF5)
>> Expected:
>> Left Integer Multiplication by Integer Ring on Finite Field of size 5
>> Got:
>> Left Integer Multiplication by Integer Ring on Finite Field of size 1
>> **
>> 1 item had failures:
>>1 of   4 in sage.structure.coerce_actions.IntegerMulAction._repr_name_
>> [143 tests, 1 failure, 3.30 s]
>> --
>> sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx  # 1
>> doctest failed
>>
>> bizarre. Maybe some kind of cache bug?
>
> Well, I've been trying to debug this for a last hour and it got pretty
> deep pretty fast.  I'm looking now at the possibility of a memory
> allocation bug in MPIR/GMP...

I see now--less likely a bug with MPIR/GMP itself, and more likely a
bug with Sage's fast_tp_new stuff for Integer.  I haven't looked too
closely at how it works yet, but in case anyone wants to take a look
there appears to be a bug where two Integers' mpz_t structs' _mp_d
member (the array of limbs) is being set to the same memory address.
They still have different mpz_t's, but since the limb array is being
shared the latter integer being initialized overrides the former.  It
seems to just happen rarely so it's to reproduce, and I just *happen*
to have found a case where it does happen pretty reliably...

I'm going home now, but that's the general synopsis if anyone wants to
take a further look at it.  I'll open a ticket tomorrow.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.beta8 released

[Erik Bray]

On Wed, Mar 14, 2018 at 8:33 PM, Jeroen Demeyer  wrote:
> On 2018-03-14 19:02, Erik Bray wrote:
>>
>> I see now--less likely a bug with MPIR/GMP itself, and more likely a
>> bug with Sage's fast_tp_new stuff for Integer.
>
>
> I don't know whether it will fix that bug or not, but there is a
> long-standing ticket to improve those hacks at
>
> https://trac.sagemath.org/ticket/17670

It's hard to say, because this bug is so subtle that any changes to
that code might make it -appear- to go away, unless I could find a
more exact way to reproduce it.  I well certainly look at the changes
that ticket proposes, but first it would be good to confirm where the
exact bug is (and, perhaps, why I'm only seeing it on Cygwin, which
may be coincidence...)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.beta8 released

[Erik Bray]

On Wed, Mar 14, 2018 at 10:03 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Congratulations Erik! You found the field with one element in SageMath:
>
>   https://en.wikipedia.org/wiki/Field_with_one_element
>
> I am really impressed.

Hah!  Yes, I was extremely confused as to why Sage was telling me I
had a field with one element.

> On 14/03/2018 16:49, Erik Bray wrote:
>>
>> I am now pretty consistently getting the following failure on Cygwin
>> with 8.2beta8 (although strangely I've run the test once or twice with
>> success too...):
>>
>> sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx
>> **
>> File "src/sage/structure/coerce_actions.pyx", line 786, in
>> sage.structure.coerce_actions.IntegerMulAction._repr_name_
>> Failed example:
>>  IntegerMulAction(ZZ, GF5)
>> Expected:
>>  Left Integer Multiplication by Integer Ring on Finite Field of size 5
>> Got:
>>  Left Integer Multiplication by Integer Ring on Finite Field of size 1
>> **
>> 1 item had failures:
>> 1 of   4 in sage.structure.coerce_actions.IntegerMulAction._repr_name_
>>  [143 tests, 1 failure, 3.30 s]
>> --
>> sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx  # 1
>> doctest failed
>>
>> bizarre. Maybe some kind of cache bug?
>>
>> On Wed, Mar 14, 2018 at 4:34 PM, Sébastien Labbé  wrote:
>>>
>>> On Ubuntu 16.04, my first attempt at running make finishes with a problem
>>> with giac (undefined reference to `png_set_longjmp_fn')
>>>
>>> The log finishes with:
>>>
>>> ...
>>> [giac-1.4.9.45.p2] libtool: link: g++ -g -O2 -fno-strict-aliasing
>>> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath
>>> -Wl,/home/slabbe/GitBox/sage/local/lib
>>> -o .libs/icas icas.o  -L/home/slabbe/GitBox/sage/local/lib
>>> ./.libs/libxcas.a
>>>
>>> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so
>>> -lntl -lpari -lreadline -ltermcap -lgsl -lgslcblas -lrt -lpthread -lglpk
>>> -ldl -lpng -lm -lmpfi /home/slabbe/GitBox/sage/local/lib/libmpfr.so -lgmp
>>> -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib
>>> [giac-1.4.9.45.p2]
>>>
>>> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so:
>>> undefined reference to `png_set_longjmp_fn'
>>> [giac-1.4.9.45.p2] collect2: error: ld returned 1 exit status
>>> [giac-1.4.9.45.p2] Makefile:579: recipe for target 'icas' failed
>>> [giac-1.4.9.45.p2] make[5]: *** [icas] Error 1
>>> [giac-1.4.9.45.p2] make[5]: Leaving directory
>>>
>>> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src'
>>> [giac-1.4.9.45.p2] Makefile:404: recipe for target 'all-recursive' failed
>>> [giac-1.4.9.45.p2] make[4]: *** [all-recursive] Error 1
>>> [giac-1.4.9.45.p2] make[4]: Leaving directory
>>> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
>>> [giac-1.4.9.45.p2] Makefile:333: recipe for target 'all' failed
>>> [giac-1.4.9.45.p2] make[3]: *** [all] Error 2
>>> [giac-1.4.9.45.p2] make[3]: Leaving directory
>>> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
>>> [giac-1.4.9.45.p2]
>>>
>>> 
>>> [giac-1.4.9.45.p2] Error building giac-1.4.9.45.p2
>>> [giac-1.4.9.45.p2]
>>>
>>> 
>>> ...
>>>
>>> I did
>>>
>>> sage -f libpng && make
>>>
>>> which seems to have fixed the error:
>>>
>>> ...
>>> [giac-1.4.9.45.p2] successfully installed.
>>> ...
>>>
>>> ... still running.
>>>
>>> Sébastien
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "sage-release" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to sage-release+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-release@googlegroups.com.
>>> Visit this group at https:/

Re: [sage-release] Re: Sage 8.2.beta8 released

[Erik Bray]

On Thu, Mar 15, 2018 at 7:26 AM, Jeroen Demeyer  wrote:
> On 2018-03-14 19:02, Erik Bray wrote:
>>
>> two Integers' mpz_t structs' _mp_d
>> member (the array of limbs) is being set to the same memory address.
>
>
> You really mean two different Integer objects with the same _mp_d (as
> opposed to the same Integer object being used mistakenly in two different
> places).

Yes--two different objects, each with their own __mpz_struct values,
but the same _mp_d.  It's not too surprising that this can happen
considering how fast_tp_new assigns to this directly.  But it's not
immediately obvious to me how the code is incorrect either.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc0 released

[Erik Bray]

On Thu, Mar 29, 2018 at 3:20 PM, Eric Gourgoulhon
 wrote:
>
>
> Le jeudi 29 mars 2018 14:16:22 UTC+2, Dima Pasechnik a écrit :
>>
>>
>>
>> On Thursday, March 29, 2018 at 12:31:15 PM UTC+1, Eric Gourgoulhon wrote:
>>>
>>> Hi,
>>>
>>> If one performs
>>> git clone https://github.com/sagemath/sage.git
>>> one gets the develop branch, not the master one:
>>> cd sage
>>> git branch -v
>>> returns
>>> * develop e5c848a Updated SageMath version to 8.2.rc0
>>>
>>> Shouldn't "git clone" yields the master branch (8.1) only ?
>>
>>
>> why? You can do
>>
>> git checkout master
>>
>> anyway...
>>
>
>
>
> Yes, but IIRC some time ago "git clone" used to yield directly the master
> branch. So it was changed at some point. I am of course fine with the new
> behaviour. It's clearly more convenient for development. However I wonder if
> this may not confuse users who would try to compile the latest *stable*
> version of Sage by getting the sources via git clone. It particular, this
> seems to contradict
> http://doc.sagemath.org/html/en/developer/walk_through.html#obtaining-the-sage-source-code

I changed it to develop for a few different reasons.  We can change it
back to 'master' for now since it contradicts the documentation, but
I'd really rather update the documentation and then change this to
work, like, closer to the way git is intended to work.  Anyways, "in
theory" the "develop" branch should still be reasonably stable, and
users who want to build from source from the latest stable release
should check out the relevant tag (we do those, right?).

A user advanced enough to want to build from source can surely figure
that out, especially if we note the latest stable version in an easy
to find way.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc1 released

[Erik Bray]

On Mon, Apr 2, 2018 at 11:09 AM, Eric Gourgoulhon
 wrote:
> Since we have entered the 8.2.rc cycle, may I ask about the status of the
> (blocker) ticket #24484 (broken export of Jupyter notebooks  to any format)
> ?
> Without it, many users might complain (it was working fine in Sage 8.1).

I'll see if I can work on finishing it, and hopefully we can get that
in the next "rc".  If it is in fact a blocker it should be treated as
such.

The raft of "last minute" issue requests for 8.2 appearing in this
thread indicates to me once again the problems with Sage's release
scheduling, or lack thereof.  Without more communication / planning of
Sage releases no one really "knows" for sure when a Sage release is
imminent until some commit happens to get tagged "rc".  *Then* it
becomes a panic of "oh, those issues I haven't been working on
(because I was busy with other things, etc.) are suddenly higher
priority", because otherwise they won't be in a final release until
after the next 3+ month development cycle.

I think this can be mitigated significantly simply by having a rough,
but published release cycle (say, one every 3 months), with cutoff
dates for non-critical issues, and reminders (to this list) of those
cutoff dates so that any people can have a chance to advocate for
and/or complete work that they hope to see in the release *before* we
start tagging things as "release candidates".

Best,
E

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc1 released

[Erik Bray]

On Tue, Apr 3, 2018 at 10:56 AM, Eric Gourgoulhon
 wrote:
> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone,
> parallel (-j16) build OK and make ptestlong reported some transient errors
> due to "Jmol failed to create file" in 4 files + a new transient (i.e.
> passed when run standalone) error:
>
> sage -t --long --warn-long 46.2 src/sage/sets/totally_ordered_finite_set.py
> **
> File "src/sage/sets/totally_ordered_finite_set.py", line 218, in
> sage.sets.totally_ordered_finite_set.TotallyOrderedFiniteSet
> Failed example:
> for e in [1,'a',(0, 0)]:
> f = A(e)
> l = (e == f,
>  cmp(e,f) == cmp(type(e),type(f)),
>  cmp(f,e) == cmp(type(f),type(e)))
> print(l)
> Expected:
> (False, True, True)
> (False, True, True)
> (False, True, True)
> Got:
> (False, False, False)
> (False, True, True)
> (False, True, True)
> **
> 1 item had failures:
>1 of  29 in sage.sets.totally_ordered_finite_set.TotallyOrderedFiniteSet
>
> All these errors disappear when the doctests are run standalone.

I am consistently getting this failure in
src/sage/sets/totally_ordered_finite_set.py when running the tests on
Cygwin, even when I just run

./sage -t src/sage/sets/totally_ordered_finite_set.py

directly.  I don't recall ever seeing such a failure previously.

Still getting the failure from https://trac.sagemath.org/ticket/24986
as well but that's to be expected since it isn't fixed yet :)

> Le dimanche 1 avril 2018 00:39:14 UTC+2, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> fb9f38a4ae (tag: 8.2.rc1) Updated SageMath version to 8.2.rc1
>> 97a9c3fe1a Trac #25025: Fix jmol package in Cygwin
>> 1fe5f21b49 Trac #25021: Update the jmol SPKG with DESTDIR support
>> c67129c035 Trac #25055: Upgrade openssl to 1.1.0h
>> f756e2ebe9 Trac #21828: Use MemoryAllocator in generic graphs; fixes crash
>> e5c848a64c (tag: 8.2.rc0) Updated SageMath version to 8.2.rc0
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc1 released

[Erik Bray]

On Tue, Apr 10, 2018 at 10:45 AM, Erik Bray  wrote:
> On Tue, Apr 3, 2018 at 10:56 AM, Eric Gourgoulhon
>  wrote:
>> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone,
>> parallel (-j16) build OK and make ptestlong reported some transient errors
>> due to "Jmol failed to create file" in 4 files + a new transient (i.e.
>> passed when run standalone) error:
>>
>> sage -t --long --warn-long 46.2 src/sage/sets/totally_ordered_finite_set.py
>> **
>> File "src/sage/sets/totally_ordered_finite_set.py", line 218, in
>> sage.sets.totally_ordered_finite_set.TotallyOrderedFiniteSet
>> Failed example:
>> for e in [1,'a',(0, 0)]:
>> f = A(e)
>> l = (e == f,
>>  cmp(e,f) == cmp(type(e),type(f)),
>>  cmp(f,e) == cmp(type(f),type(e)))
>> print(l)
>> Expected:
>> (False, True, True)
>> (False, True, True)
>> (False, True, True)
>> Got:
>> (False, False, False)
>> (False, True, True)
>> (False, True, True)
>> **
>> 1 item had failures:
>>1 of  29 in sage.sets.totally_ordered_finite_set.TotallyOrderedFiniteSet
>>
>> All these errors disappear when the doctests are run standalone.
>
> I am consistently getting this failure in
> src/sage/sets/totally_ordered_finite_set.py when running the tests on
> Cygwin, even when I just run
>
> ./sage -t src/sage/sets/totally_ordered_finite_set.py
>
> directly.  I don't recall ever seeing such a failure previously.

Oh, I just realized this is fixed by https://trac.sagemath.org/ticket/25077


>> Le dimanche 1 avril 2018 00:39:14 UTC+2, Volker Braun a écrit :
>>>
>>> As always, you can get the latest beta version from the "develop" git
>>> branch. Alternatively, the self-contained source tarball is at
>>> http://www.sagemath.org/download-latest.html
>>>
>>> fb9f38a4ae (tag: 8.2.rc1) Updated SageMath version to 8.2.rc1
>>> 97a9c3fe1a Trac #25025: Fix jmol package in Cygwin
>>> 1fe5f21b49 Trac #25021: Update the jmol SPKG with DESTDIR support
>>> c67129c035 Trac #25055: Upgrade openssl to 1.1.0h
>>> f756e2ebe9 Trac #21828: Use MemoryAllocator in generic graphs; fixes crash
>>> e5c848a64c (tag: 8.2.rc0) Updated SageMath version to 8.2.rc0
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-release" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-release+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc2 released

[Erik Bray]

On Wed, Apr 11, 2018 at 6:59 PM, Eric Gourgoulhon
 wrote:
> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone +
> pull develop, parallel (-j16) build OK and make ptestlong passed except for
> a single transient error to due to "Jmol failed to create file", as usual on
> this computer (race error?). The doctest is passed when run standalone.

That's weird about jmol--I haven't seen that, but I don't think the
Linux machine I do most builds on has a Java runtime installed so of
course I wouldn't see it.  I should try to reproduce that at some
point if I can...

Looks fine on Windows but still needs this critical patch for the
tests before release:

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc2 released

[Erik Bray]

On Thu, Apr 12, 2018 at 11:09 AM, Erik Bray  wrote:
> On Wed, Apr 11, 2018 at 6:59 PM, Eric Gourgoulhon
>  wrote:
>> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone +
>> pull develop, parallel (-j16) build OK and make ptestlong passed except for
>> a single transient error to due to "Jmol failed to create file", as usual on
>> this computer (race error?). The doctest is passed when run standalone.
>
> That's weird about jmol--I haven't seen that, but I don't think the
> Linux machine I do most builds on has a Java runtime installed so of
> course I wouldn't see it.  I should try to reproduce that at some
> point if I can...
>
> Looks fine on Windows but still needs this critical patch for the
> tests before release:

Didn't mean to send.  Still needs these patches for Windows:

https://trac.sagemath.org/ticket/25107
https://trac.sagemath.org/ticket/25137

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.2.rc3 released

[Erik Bray]

Thanks for getting the other two Cygwin issues fixed!  It looks good
to me.  However, there is still a problem
https://trac.sagemath.org/ticket/25150  still needs to be fixed--I'd
be perfectly open to a different solution if the one I've suggested is
bad.

On Tue, Apr 17, 2018 at 12:34 AM, Volker Braun  wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> a9d274b933 (tag: 8.2.rc3, trac/develop) Updated SageMath version to 8.2.rc3
> d85d03cfc3 Trac #25051: Add DESTDIR support to additional Python packages;
> upgrade pip to latest patch release
> ab932bd4d3 Trac #23969: Downgrade cryptominisat to experimental
> 9bac572eb4 Trac #25107: Ignored OSErrors in test output on Cygwin
> 3d4ffb3923 Trac #25092: sage --gdb does not start due to SIGFPE
> f150587302 Trac #25137: Temporarily skip the test that causes #24986
> 303efaa461 (tag: 8.2.rc2) Updated SageMath version to 8.2.rc2
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc4 released

[Erik Bray]

On Sat, Apr 21, 2018 at 5:03 PM, John H Palmieri  wrote:
>
>
> On Saturday, April 21, 2018 at 1:28:18 AM UTC-7, Volker Braun wrote:
>>
>> At the end of the day, this just wastes some time on initial build -> not
>> a blocker. If somebody comes up with a fix in the next 24h I'll merge it.
>
>
> Has the CEO declared some deadline for the release? I must have missed that.
> Otherwise, why release flawed software that will inconvenience anyone
> building on OS X? It's the second build, not the initial build – if you
> don't remember that it's an issue, it's the second build. So the typical
> workflow will be: run make, switch to another branch to do some development,
> run make again, at which point you have to wait for an hour and half even
> though you just touched one py file. So as long as this is a bug, you have
> to run make twice to get something usable for development.

+1

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc4 released

[Erik Bray]

On Thu, Apr 26, 2018 at 11:16 AM,   wrote:
> Hello,
>
> can we hope to have 8.2 released and move on to 8.3.beta soon ? I am really
> worried by the 161 positive-reviewed tickets that have been accumulating,
> and by the potential rebase work that will be triggered.

I know there are supposed issues related to continuous integration
(which I would think are fixable) but on a normal project it's
possible to create a branch (e.g. 8.2-release) into which only patches
intended for that release are merged, while new patches can still be
merged into the master branch so that development can proceed apace.

But I'm told that's somehow impossible for Sage.


> Le vendredi 20 avril 2018 22:28:15 UTC+2, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> This should be the last rc, so if you want to test it now is the right
>> time!
>>
>> f46abe6c0e (tag: 8.2.rc4, trac/develop) Updated SageMath version to
>> 8.2.rc4
>> 88f80f584b Trac #25217: Fix test regression in banner()
>> cee7c1d6d3 Trac #25196: sage -gdb abort
>> 8fc1b6ad67 Trac #25177: cython() does not work in Jupyter
>> b47963fb84 Trac #25078: ./sage -f sagelib no longer works
>> a9d274b933 (tag: 8.2.rc3) Updated SageMath version to 8.2.rc3
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc4 released

[Erik Bray]

On Thu, Apr 26, 2018 at 12:38 AM,   wrote:
> On Wednesday, April 25, 2018 at 2:31:55 PM UTC-7, Steven Trogdon wrote:
>> Is this a consequence of fixing the banner
>>
>>
>>
>> LC_ALL=C ./sage
>> SageMath version 8.2.rc4, Release Date: 2018-04-20
>>
>> and thus no banner, or has it always been this way? I only noticed because I 
>> had changed LC_ALL for some other purpose. I usually have LC_ALL unset with 
>> the other LC_ variables set individually.
>
> Yes, it is. With LC_ALL=C we get:
>
> sage: print(sage.misc.banner.banner_text())
> UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-69: 
> ordinal not in range(128)
>
> Previously, the banner was written into a file at build-time and displayed by 
> "cat"ing that file, so the contents of the file didn't pass through a Python 
> codec at runtime.
>
> I think python is basically correct in doing this: if the locale is C then 
> only ascii should be sent to the stdout, right?

Yes, that's more or less the correct behavior in the current Python
(although there are proposals to force Python to use LC_CTYPE=C.UTF-8
if LC_CTYPE=C).  But if the current locale uses a non-unicode encoding
then it assumes to only send ASCII.

The sage.misc.banner.banner() function catches that UnicodeEncodeError
and returns the plain banner.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc4 released

[Erik Bray]

On Thu, Apr 26, 2018 at 3:55 PM, Jeroen Demeyer  wrote:
> On 2018-04-26 12:29, Erik Bray wrote:
>>
>> But I'm told that's somehow impossible for Sage.
>
>
> I don't think that it's fundamentally impossible. But it would require
> changes to certain tools. For example, which branch should the patchbot use?
>
> Allow me to mention what I did when I was release manager: I also always had
> a linear release history, but I already started working privately on future
> releases, merging tickets and testing them on the buildbot. So once a final
> release was made, tickets were fully ready to be merged in the next beta. If
> there was a sufficient backlog, this would for example mean that Sage 8.2,
> 8.3.beta0 and 8.3.beta1 would be released all on the same day.

If there were release branches (say, release-8.1, release-8.2, etc.)
that are more or less equivalent to what you described, the patchbot
runner (as long as we're still even using it :) could be configured to
build tickets intended for those milestones either only against those
branches (if they exist) or against the latest "develop", or both.
Under the current process you might only make a release- branch
alongside the first release candidate.  That's the point at which you
want to curtail exactly which changes get merged, so that a releasable
product can be converged on.

Given such a branch to work in, it becomes less "urgent" to finish a
release since it no longer needs to block normal development progress.
Of course, you still don't want to spend forever getting a release
out, but at least the release itself doesn't become a blocker.

Updating the tooling (the patchbot, etc.) is not so terrible.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.2.rc4 released

[Erik Bray]

On Sat, May 5, 2018 at 10:21 PM,   wrote:
> On Thursday, April 26, 2018 at 7:11:52 AM UTC-7, Erik Bray wrote:
>>
>>
>> Given such a branch to work in, it becomes less "urgent" to finish a
>> release since it no longer needs to block normal development progress.
>> Of course, you still don't want to spend forever getting a release
>> out, but at least the release itself doesn't become a blocker.
>>
> Having some urgency to completing a release once it's decided to start it is
> probably beneficial as a whole.
>
> However, in the current situation we've have sage8.2rc0 more than a month
> ago and progress on the development branch is at a complete standstill at
> the moment. I don't think this is healthy for the project. I don't have the
> time or expertise to help with that myself, but I hope others do and are
> able to dislodge the current jam.

My suggestion for how to resolve this seems obvious and
straightforward.  The only objection I've seen is "but what will the
patchbots do?"  But with a better documented process that is easily
resolved.

If it's not clear, shall I write up some more formal documentation for
my proposed process?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Release process

[Erik Bray]

On Mon, May 7, 2018 at 4:55 PM, Jeroen Demeyer  wrote:
> (starting a new thread for the discussion about the current very slow pace
> of merging tickets)
>
> On 2018-05-07 16:28, Erik Bray wrote:
>>
>> If it's not clear, shall I write up some more formal documentation for
>> my proposed process?
>
>
> To be honest, I think it's not very meaningful to do that without consulting
> the release manager. I mean, you can write up all the documentation that you
> want; in the end, it's the release manager who decides what happens.

Sure, that goes without saying.  That doesn't mean it isn't a good
idea to document an idea more carefully for the review of all those
involved.  Such documentation would only be an initial draft.
Unfortunately Sage development does not have a PEP-like process in any
formal sense either.  Maybe it should.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Release process

[Erik Bray]

On Sat, May 12, 2018 at 10:31 AM, Marc Mezzarobba  wrote:
> Jeroen Demeyer wrote:
>> To be honest, I think it's not very meaningful to do that without
>> consulting the release manager. I mean, you can write up all the
>> documentation that you want; in the end, it's the release manager who
>> decides what happens.
>
> Even without switching to the model Erik is advocating, it could perhaps
> be useful to have additional integration branches where the *reviewer*
> would be supposed to merge a branch when setting the corresponding
> ticket to positive review. The release manager would remain free to use
> these branches or not when preparing the actual release.

I mean, one thing that drives me up the wall is being told with some
regularity that a ticket of mine has a "merge conflict" without any
indication of what it actually *conflicts* with, even though the
ticket merges fine with the "develop" branch.  This is because Volker
has a "private" integration branch that he's merging things into.
(I've in the past glibly called this "secret", and while no it's not
*actually* secret it's not exactly easy to find--I don't understand
why it isn't just a standard branch like "master", or at least
something with an identifiable name that is fetched by default).
While Volker could at least tell us what the conflicting files are we
are otherwise left to guess since we don't even know what's been
merged into that branch.  I think it would be better if this branch
were easily found and were documented--yes its contents may change and
shift rapidly, but for a sophisticated developer who just wants to
peek in on the release process this is not a problem.

All that said, I see no reason not to make release-specific branches.
On most projects I would make such a branch simultaneously with
tagging a beta release of a new X.Y version.  Sage's development
process uses "beta" a little differently that I would normally, and
that's fine--that's just a bikeshed.  But with Sage's version
nomenclature it would at least make sense to create a release-specific
branch concurrently with the first *release candidate*.  With such a
branch available, development can still continue apace while critical
bugfixes can be backported the release branch.  This is a completely
normal thing to do and is plenty advantageous.  I don't see the harm
in asking people who are interested in Sage development to get used to
the idea that there can be multiple lines of development
simultaneously (in this case just two...)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Release process

[Erik Bray]

On Tue, May 15, 2018 at 2:16 PM, Maarten Derickx
 wrote:
>
>
> On Tuesday, 15 May 2018 12:35:52 UTC+2, Erik Bray wrote:
>>
>> On Sat, May 12, 2018 at 10:31 AM, Marc Mezzarobba 
>> wrote:
>> > Jeroen Demeyer wrote:
>> >> To be honest, I think it's not very meaningful to do that without
>> >> consulting the release manager. I mean, you can write up all the
>> >> documentation that you want; in the end, it's the release manager who
>> >> decides what happens.
>> >
>> > Even without switching to the model Erik is advocating, it could perhaps
>> > be useful to have additional integration branches where the *reviewer*
>> > would be supposed to merge a branch when setting the corresponding
>> > ticket to positive review. The release manager would remain free to use
>> > these branches or not when preparing the actual release.
>>
>> I mean, one thing that drives me up the wall is being told with some
>> regularity that a ticket of mine has a "merge conflict" without any
>> indication of what it actually *conflicts* with, even though the
>> ticket merges fine with the "develop" branch.  This is because Volker
>> has a "private" integration branch that he's merging things into.
>> (I've in the past glibly called this "secret", and while no it's not
>> *actually* secret it's not exactly easy to find--I don't understand
>> why it isn't just a standard branch like "master", or at least
>> something with an identifiable name that is fetched by default).
>> While Volker could at least tell us what the conflicting files are we
>> are otherwise left to guess since we don't even know what's been
>> merged into that branch.  I think it would be better if this branch
>> were easily found and were documented--yes its contents may change and
>> shift rapidly, but for a sophisticated developer who just wants to
>> peek in on the release process this is not a problem.
>>
>
>
> I think the fact that this branch is "secret" is a feature instead of an
> annoyance. It prevents us the eager developers from random rebasing branches
> of one ticket onto the branch of another ticket. Which is a good thing if
> you take into account with how Linus intends git to be used
> https://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html
> (summary you should only rebase/merge with things that are in a "nice"
> state). The reason for Volker not advertising his branch is that he wants to
> have full freedom in changing the branch in whatever way he sees fit.

I'm not convinced that's a real problem.  This is what I meant by "yes
its contents may change and shift rapidly, but for a sophisticated
developer who just wants to peek in on the release process this is not
a problem".  For my own purposes I would be doing things like "git
fetch upstream; git checkout "integration"; git reset --hard
upstream/integration" where "integration" is just a stand-in name I'm
using for this hypothetical branch.  Then I can easily do something
like "git checkout tmp-merge; git merge my-branch" to see how my
branch currently works with other branches being currently integrated,
instead of just being told "merge conflict ¯\_(ツ)_/¯" with no means of
investigating for myself :)

> I think having the release manager determine what is stable enough to go
> into the next beta is a sensible thing to do, and that we as developers
> should only rebase onto the next beta is also sensible.

I don't know if that's actually what's happening though.
That determination is partly based on "does the ticket have positive
review" and the rest is opaque.

Anyways, my original purpose of this thread was just asking if I
should bother proposing a process for creating release branches so
that we don't have such a bottleneck when it comes to creating
releases.  I'm not sure I'm convinced by the suggestion that 8.2 was
an aberration, because I feel like this has been a problem for every
Sage release I've witnessed to some degree or other, and to a greater
degree than I've ever seen elsewhere.

> That being said, I do think that a better communication about why things are
> done in the way they are could help a lot with migitating the annoyances.
> I.e. instead of just a comment "merge conflict" on trac by Volker, there
> would instead just post "merge conflict + pointer to sage developer manual"
> where the pointer to the sage developer manual is a pointer to a to be
> written part of the developer manual that explains what the "merge conflict"
> means, and why it is best to just wait till the next beta.

I wouldn't find that any more helpful.

Best,
E

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Release process

[Erik Bray]

On Tue, May 15, 2018 at 3:11 PM, Jeroen Demeyer  wrote:
> On 2018-05-15 14:35, Erik Bray wrote:
>>
>> I'm not convinced that's a real problem.  This is what I meant by "yes
>> its contents may change and shift rapidly, but for a sophisticated
>> developer who just wants to peek in on the release process this is not
>> a problem".
>
>
> I agree that it's not a problem for the "sophisticated developer" who knows
> what he is doing. But the more you advertise this secret branch, the larger
> chance there is of abuse by non-sophisticated developers who have no clue. I
> believe that this is the point that Maarten was trying to make.

I don't see much chance for "abuse".  Mostly all I'm talking about
here is to do integration in a branch that's easy to identify and is
documented (it can even be documented as "this branch is unstable so
don't look at it unless you know what you're doing".  The worse
someone can bite themselves is by maybe rebasing a branch on top of
that branch, and then proposing that version of the branch for merging
which might not always be for the best (though it might often be fine
too).  To make this mistake would require knowing how to use rebase in
the first place...

On Tue, May 15, 2018 at 3:49 PM, Jeroen Demeyer  wrote:
> On 2018-05-15 15:40, Emmanuel Charpentier wrote:
>>
>> Therefore, I think that contributing to Sage should not *require* a
>> sophisticated understanding of the finer points of git care and feeding...
>
>
> Of course not. I don't think that anybody here proposed that.

Nope, but as I wrote upthread this discussion is still orthogonal to
what I wanted to propose...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.3.beta1 released

[Erik Bray]

Thanks for the release.

On Ubuntu 14.04 I get LOTS of test timeouts that I didn't get
previously.  It's possible though that the system is just uder heavy
load, but even re-running the tests with --failed keeps giving me
timeouts for some modules.  So I'm concerned about a real performance
regression somewhere.  I'm running ./sage -t -a --failed yet again,
but from my last run I got:

sage -t src/sage/libs/gap/all_documented_functions.py  # Timed out
sage -t src/sage/libs/gap/assigned_names.py  # Timed out
sage -t src/sage/manifolds/differentiable/affine_connection.py  # Timed out
sage -t src/sage/manifolds/differentiable/euclidean.py  # Timed out
sage -t src/sage/manifolds/differentiable/metric.py  # Timed out
sage -t src/sage/manifolds/differentiable/multivectorfield.py  # Timed out
sage -t src/sage/manifolds/differentiable/tensorfield.py  # Timed out
sage -t src/sage/plot/plot.py  # Timed out
sage -t src/sage/rings/padics/padic_base_leaves.py  # Timed out
sage -t src/sage/rings/padics/padic_lattice_element.py  # Timed out
(and interrupt failed)


Will try 16.04 (the current base for my Docker images) and 18.04 next.

On Tue, May 15, 2018 at 2:46 PM, Emmanuel Charpentier
 wrote:
> FWIW : on Debian testing running on Core i7 + 16 GB RAM, same results as for
> 8.3.beta0, i. e. one transient and two permanent errors (the same as before)
> :
>
> --
> sage -t --long src/sage/rings/padics/padic_lattice_element.py  # Timed out
> sage -t --long src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed
> sage -t --long src/sage/features/gap.py  # 1 doctest failed
> --
>
> HTH,
>
> --
> Emmanuel Charpentier
>
>
> Le lundi 14 mai 2018 20:10:54 UTC+2, Volker Braun a écrit :
>>
>> As always, you can get the latest beta version from the "develop" git
>> branch. Alternatively, the self-contained source tarball is at
>> http://www.sagemath.org/download-latest.html
>>
>> 6fc1e20c66 (tag: 8.3.beta1) Updated SageMath version to 8.3.beta1
>> 8c327b9901 Trac #25258: Gurobi breaks lots of doctests in make ptestlong
>> 47a7327e12 Trac #25248: py3: fix sage.parallel.map_reduce
>> 7feb4d298c Trac #25244: LatticePoset: Add is_interval_dismantlable
>> 3e6075d57b Trac #25236: Deprecate various functions from old coercion
>> model
>> c4b415fa9f Trac #25235: q-Stirling numbers of the second kind
>> 2c90815686 Trac #25224: Mismatch in the definition of dilog() between
>> fricas and sympy
>> 3ab97b15d3 Trac #25223: Cleaning of the usage of BFS
>> bf0beabf6a Trac #25220: fix definite fricas integration
>> 88e1ed6d0e Trac #25216: py3: fix bytes handling bugs in sage.plot.animate
>> deae517486 Trac #25211: code should not depend ordering of codegrees
>> eb2f271af2 Trac #25203: Speed up FiniteField.zeta()
>> 22b8be8a05 Trac #25201: Use super() in MatrixSpace.__getitem__
>> 9a7f40d097 Trac #25200: Incorrect long element for signed permutations
>> eba77d3f14 Trac #25195: py3: fix segfault in element wrapper on Python 3
>> f5527d2184 Trac #25192: primitivity test for integral matrices
>> b3b4f75048 Trac #25186: Use ZZ.random_element for random_prime
>> 7e6c6ab9e5 Trac #25182: coherent output type for polynomial.degree()
>> 6aafae Trac #25174: conversion of I to fricas is wrong
>> 6a34919efb Trac #25169: py3: fixing print in sage-starts script
>> 80d4a17edc Trac #25161: Sphinx build hangs when a BaseException occurs
>> 6f130ae999 Trac #25146: Cleanup of AbstractPartitionDiagram
>> 41c9fffbe1 Trac #24966: package primecount 4.3
>> 72980a10a1 Trac #24890: Tensor product of lattices
>> 951fa49129 Trac #24460: py3: fixes to sage.libs.gap
>> e5af4884cc Trac #15508: Implement Fock space
>> 4756f04cbe Trac #25335: Missing imports in
>> src/sage/geometry/polyhedron/base.py
>> faad356119 Trac #25133: Implement WQSym
>> b593af3371 Trac #25132: Define the class of SuperPartitions
>> c1a36a02ee Trac #25131: FQSym: add G basis
>> ad72cec5b8 Trac #25128: Have py_scalar_to_element convert gmpy2 numbers
>> 81f7d7a341 Trac #25121: fix edge color format in graphviz_string
>> 8821bb1454 Trac #25120: dot2tex edge coloring is broken
>> 80fa1be913 Trac #25117: some pyflakes cleanup for unused variables
>> fd8c5d4676 Trac #25112: perl_term_readline_gnu: Upgrade to 1.35 and patch
>> away ncurses problem
>> bf6cbafbed Trac #25109: Upgrade cmake to 3.11.0
>> 07ce7c88bf Trac #25105: ell_number_field.py takes a long time to test
>> bb996e69ec Trac #25098: Fix LaTeX usage in Rings documentation
>> eecf07e8c7 Trac #25095: polygon3d ignores the "alpha" (and equivalent
>> "opacity") argument
>> 15b5aa2b60 Trac #25081: The polar of a polyhedron should carry the backend
>> used.
>> 62a893aba3 Trac #25080: code for Cartesian factorization of posets
>> 89ec1fb5c2 Trac #25075: pyflakes cleanup in combinat
>> 329c579bac Trac #25074: upgrade to ipywidgets 7.2.0
>> a5122d141e Trac #25067: Implement quantum group q-numbers
>> 054122ae77 Trac #25

Re: [sage-release] Re: Sage 8.3.beta1 released

[Erik Bray]

On Wed, May 16, 2018 at 9:56 AM, John Cremona  wrote:
> I started to build this yesterday after pulling from trac into a place where
> beta0 had already built OK.  This morning I find the lines
>
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
> [scipy-0.19.1] Skipping scipy as it is not installed.
>
> being repeated for ever.  I have left that going in case someone wants to
> see any log files.

I'm not sure, but I think this might be pip-related.  I think Jeroen
mentioned something about this to me a couple weeks ago.  Is it
possible you upgraded the pip in your Sage install?



> On 16 May 2018 at 08:44, Henri Girard  wrote:
>>
>> Bionic 18.04 AMD x8 64 bits, compile perfect. I started from fresh git
>> sage because upgrading from 8.2 failed. It couldn't find many libs. By the
>> way I found my crash problem while compiling : I had to config the bios
>> allowing warmer processing.
>>
>>
>> Le 15/05/2018 à 21:24, Sébastien Labbé a écrit :
>>
>> On Ubuntu 16.04, the command `./sage -t -p --all --long
>> --optional=sage,optional,external` finishes with:
>>
>> --
>> sage -t --long src/sage/coding/code_constructions.py  # 1 doctest failed
>> --
>> Total time for all tests: 1821.3 seconds
>> cpu time: 11639.5 seconds
>> cumulative wall time: 14059.4 seconds
>> External software detected for doctesting: gurobi,latex
>> Traceback (most recent call last):
>>   File "/home/slabbe/GitBox/sage/src/bin/sage-runtests", line 127, in
>> 
>> err = DC.run()
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
>> line 1176, in run
>> + ','.join(available_software.seen()))
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
>> line 583, in log
>> self.logger.write(s + end)
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
>> line 250, in write
>> f.write(x)
>> ValueError: I/O operation on closed file
>>
>>
>> The code_construction error is copied below (I can not reproduce it) :
>>
>>
>>
>> sage -t --long src/sage/coding/code_constructions.py
>> **
>> File "src/sage/coding/code_constructions.py", line 624, in
>> sage.coding.code_constructions.QuadraticResidueCodeOddPair
>> Failed example:
>> codes.QuadraticResidueCodeOddPair(17, GF(13))
>> Exception raised:
>> Traceback (most recent call last):
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 562, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 972, in compile_and_execute
>> exec(compiled, globs)
>>   File "> sage.coding.code_constructions.QuadraticResidueCodeOddPair[0]>", line 1, in
>> 
>> codes.QuadraticResidueCodeOddPair(Integer(17), GF(Integer(13)))
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/coding/code_constructions.py",
>> line 666, in Quadratic
>> ResidueCodeOddPair
>> return DuadicCodeOddPair(F,Q,N)
>>   File
>> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/coding/code_constructions.py",
>> line 425, in DuadicCod
>> eOddPair
>> gg1 = P2(coeffs1)
>>   File "sage/structure/parent.pyx", line 920, in
>> sage.structure.parent.Parent.__call__ (build/cythonized/sage/structure/paren
>> t.c:9734)
>> return mor._call_(x)
>>   F

Re: [sage-release] Sage 8.4.beta0 released

[Erik Bray]

On Sun, Aug 5, 2018 at 12:34 PM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html

Ubuntu 14.04, make ptestlong, all tests passed!

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta0 released

[Erik Bray]

On Mon, Aug 6, 2018 at 5:47 PM Erik Bray  wrote:
>
> On Sun, Aug 5, 2018 at 12:34 PM Volker Braun  wrote:
> >
> > As always, you can get the latest beta version from the "develop" git 
> > branch. Alternatively, the self-contained source tarball is at 
> > http://www.sagemath.org/download-latest.html
>
> Ubuntu 14.04, make ptestlong, all tests passed!

On Cygwin with make ptestlong I got:

sage -t --long src/sage/tests/cmdline.py  # 4 doctests failed
sage -t --long src/sage/combinat/symmetric_group_algebra.py  # 39
doctests failed
sage -t --long src/sage/misc/sagedoc.py  # 1 doctest failed
sage -t --long src/sage/numerical/backends/logging_backend.py  #
Killed due to abort

Most of the failures seemed to be due to timeouts, which is not
unusual on Cygwin (some of the tests take longer in general).  Three
of them passed when re-run, but

sage -t --long src/sage/misc/sagedoc.py

keeps failing with:

sage -t --long src/sage/misc/sagedoc.py
**
File "src/sage/misc/sagedoc.py", line 1175, in sage.misc.sagedoc.?
Failed example:
len(search_doc('tree', whole_word=True,
interact=False).splitlines()) < 2000  # long time
Expected:
True
Got:
False
**
1 item had failures:
   1 of  28 in sage.misc.sagedoc.?
[106 tests, 1 failure, 394.30 s]


which I've never seen before, and it's not obvious why that would have
started failing now.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta0 released

[Erik Bray]

On Tue, Aug 7, 2018 at 10:41 AM Erik Bray  wrote:
>
> On Mon, Aug 6, 2018 at 5:47 PM Erik Bray  wrote:
> >
> > On Sun, Aug 5, 2018 at 12:34 PM Volker Braun  wrote:
> > >
> > > As always, you can get the latest beta version from the "develop" git 
> > > branch. Alternatively, the self-contained source tarball is at 
> > > http://www.sagemath.org/download-latest.html
> >
> > Ubuntu 14.04, make ptestlong, all tests passed!
>
> On Cygwin with make ptestlong I got:
>
> sage -t --long src/sage/tests/cmdline.py  # 4 doctests failed
> sage -t --long src/sage/combinat/symmetric_group_algebra.py  # 39
> doctests failed
> sage -t --long src/sage/misc/sagedoc.py  # 1 doctest failed
> sage -t --long src/sage/numerical/backends/logging_backend.py  #
> Killed due to abort
>
> Most of the failures seemed to be due to timeouts, which is not
> unusual on Cygwin (some of the tests take longer in general).  Three
> of them passed when re-run, but
>
> sage -t --long src/sage/misc/sagedoc.py
>
> keeps failing with:
>
> sage -t --long src/sage/misc/sagedoc.py
> **
> File "src/sage/misc/sagedoc.py", line 1175, in sage.misc.sagedoc.?
> Failed example:
> len(search_doc('tree', whole_word=True,
> interact=False).splitlines()) < 2000  # long time
> Expected:
> True
> Got:
> False
> **
> 1 item had failures:
>1 of  28 in sage.misc.sagedoc.?
> [106 tests, 1 failure, 394.30 s]
>
>
> which I've never seen before, and it's not obvious why that would have
> started failing now.

I created a ticket for this with a proposed fix:
https://trac.sagemath.org/ticket/26017

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.3 released

[Erik Bray]

On Thu, Aug 9, 2018 at 4:48 PM Harald Schilly  wrote:
>
>
>
> On Friday, August 3, 2018 at 1:47:49 PM UTC+2, Volker Braun wrote:
>>
>> The "master" git branch has been updated to Sage-8.3. As always, you can get 
>> the latest beta version from the "develop" git branch. Alternatively, the 
>> self-contained source tarball is at 
>> http://www.sagemath.org/download-latest.html
>
>
>
> Hi, I'm  wondering, what's the status of the binary builds? I'm just curious.

Windows is in progress right now.  The rest I can't speak to.

I wonder if these announcements shouldn't make explicit that it's a
source-only release, with binary releases to be announced separately,
or something...?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta1 released

[Erik Bray]

On Thu, Aug 16, 2018 at 12:03 AM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> 23a2b10da6 (tag: 8.4.beta1) Updated SageMath version to 8.4.beta1
> 3d7965cb6f Trac #25523: Raise Exception if DynamicalSystem initialized with 
> coeffs not in given domain
> 703aa6e339 Trac #25446: compute all orbits of minimal models of dynamical 
> systems
> 18ee14bee3 Trac #25441: Allow more substitutions for non-classical rational 
> function field valuations
> a4e70dddc9 Trac #25360: Honor global proof setting for "polynomial" in 
> factorization code
> a5c0546809 Trac #25241: fix issue with change_ring for polynomials with Maps
> ef293c6e38 Trac #25229: Fix bug in BooleanMonomialMonoid._element_constructor_
> 4c940be147 Trac #25226: Do not sort inductive valuations
> 8f6c04568e Trac #23430: Cannot create a RealBall with rational radius
> 2cffe40b73 Trac #22345: Elliptic curve isogenies over number fields II: 
> implement Billerey's algorithm for reducible primes
> 912e88cfbe Trac #22157: Add SPQR-tree decomposition for 2-vertex-connected 
> graphs
> db0b3a5a48 Trac #22156: Clarifying eps_abs and eps_rel in numerical_integral
> a3e4977917 Trac #21946: solve(x==x, x) returns [x == r1]
> 705d59f725 Trac #26025: Sage should not use GP_DATA_DIR
> cf8a36f533 Trac #26020: py3: src/sage/numerical/backends/glpk_graph_backend
> 2bd1923f8a Trac #26013: lots of warnings when uninstalling spkgs
> cbe8c4550f Trac #25939: error in Well's algorithm for canonical height
> 6fb4f97eb3 Trac #25749: fixing invalid escape sequences in modular (final)
> c96ee846de Trac #25315: Find libraries in DYLD_LIBRARY_PATH as fallback
> df9d24fd40 Trac #25276: Bugs with GradedCommutativeAlgebra
> 2274331e6e Trac #26012: Fix bug concerning restrictions of tensorfields
> e674750080 Trac #26008: Upgrade setuptools and pip
> eeb4a217fb Trac #26002: Support pari compiled with threads
> 0e78774b03 Trac #25999: Compile errors due to struct
> f32c9bd7dc Trac #25984: Minor cleanup related to Monsky-Washnitzer
> ce3cf8444f Trac #25975: py3: small fix for Lfunction names
> c087f48b43 Trac #25974: py3: fix unnecessary map() in sage.calculus.riemann
> 4273770ad2 Trac #25970: Improve "Inverse does not exist" error messages
> 42694c6526 Trac #25966: Upgrade Arb to 2.14.0
> 0f3a8439b3 Trac #25144: Add DESTDIR support for palp
> ed1a6bd434 Trac #25103: Minimal polynomials of elements in p-adic fields
> 2e783bb5a8 Trac #24843: Issue with p-adic printing
> dc76f7d1fd Trac #24669: Re-enable threads on OpenBLAS
> 5e6587ef2e Trac #23218: Ramified extensions of general p-adic rings and fields
> f1ef83ac07 Trac #26021: tides does not build on 32-bit systems
> 1389c4f117 Trac #25722: Test jupyter kernel symlinks in tmpdir
> c694dfe2ed Trac #26007: Missing sagelib dependencies
> 77cf54bfb2 Trac #23627: Update points() in projective_homset.py  and 
> affine_homset.py to work over CC and CDF
> 8e656e77aa Trac #25697: Implement enumeration over QQ for product projective 
> schemes
> a12e31cdbc Trac #25781: add Comparison operator for morphism between product
> 32c9872c18 Trac #25792: add dehomogenize function for product projective point
> 7687c443b9 Trac #25821: implement height functions for product points
> 6451eb7c7f Trac #25958: py3: clean up use of map/filter in 
> sage.graphs.generators.classical_geometries
> d0ef067dd1 Trac #25947: py3: miscellaneous map -> list fixes
> 73c89a342d Trac #25940: Python 3: Chain complex fixes
> 4553736c25 Trac #25935: Make __eq__ and __hash__ of AbelianGroup_class 
> consistent
> b9bdea5ef1 Trac #25926: Cleanup generalized_Young_walls documentation
> 915800af78 Trac #25923: cleanup of any(...) outside of schemes folder
> 302de5422d Trac #25920: some changes about all() and any() in schemes
> 8992f88bb4 Trac #25918: Queer supercrystals
> 99023a94b7 Trac #25917: Add definition of crystal to catalog of crystals
> 574d72f1db Trac #25908: Printing of p-adic extensions
> fc68b6b1ec Trac #25906: Upgrade to zeromq 4.2.5 and pyzmq 17.1.0
> 2a82aeb5e5 Trac #25835: Move gap packages to features
> 6081d6f06d Trac #25345: Make it possible to test sage without htmldoc
> 0d3e496088 Trac #25602: implement translation of fricas.rootOf
> 807bf5b461 Trac #25596: Add random tests for finite posets
> 6dd6958964 Trac #25083: Upgrade to IPython 5.8
> 4664730ffe Trac #24883: Endless symbolic computation
> 8fdfaa1607 Trac #22415: Add operator class membership tests for matrices
> ada43b34b3 (tag: 8.4.beta0, trac/develop) Updated SageMath version to 
> 8.4.beta0

On Cygwin: Incremental upgrade from 8.4.beta0 built fine.

With

$ make ptestlong

I got the following failures:

--
sage -t --long src/sage/tests/py3_syntax.py  # 3 doctests failed
sage -t --long src/sage/graphs/generators/families.py  # 1 doctest failed
sage -t --long src/sage

Re: [sage-release] Sage 8.4.beta2 released

[Erik Bray]

Thanks for the beta--the inclusion of #25907 made a big difference for
running the test suite on Cygwin--many fewer errors caused by running
out of memory while running the tests :)

I did get one strange failure I have never seen before:

sage -t --long --warn-long 304.2 src/sage/parallel/map_reduce.py
**
File "src/sage/parallel/map_reduce.py", line 281, in sage.parallel.map_reduce
Failed example:
st = pstats.Stats(prof+'0')
Expected nothing
Got:
Exception AssertionError: AssertionError('TripleDictEraser: key
match but no weakref match',) in

ignored
**
1 item had failures:
   1 of  48 in sage.parallel.map_reduce
[300 tests, 1 failure, 61.63 s]


It worked when I tested that module by itself.  Anyone have any ideas?
On Sun, Aug 26, 2018 at 1:54 AM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> 8b4f9a0885 (tag: 8.4.beta2, trac/develop) Updated SageMath version to 
> 8.4.beta2
> e83762e051 Trac #26118: sage -tp times out on a 160 core machine
> c66273f117 Trac #24655: Automatically build  docker images with 
> CircleCI/GitLab CI
> f60348ff7c Trac #16268: Better normalization for fraction field elements
> db0b57b8a9 Trac #6106: Extra doctests for indefinite binary quadratic forms
> 858c733732 Trac #26094: py3: hash for noncommutative ideals
> 2f2562493d Trac #26093: py3: hash for spaces of modular symbols
> cf41f66c53 Trac #26092: py3: hash for subsets
> 09c82f55fa Trac #26089: py3: hash for smooth character groups
> 4ea5edfb9b Trac #26087: py3: hash for cycle index rings
> f8c5ba64d7 Trac #26082: py3: let pip use the correct python
> ec4a0a870f Trac #26010: Split database_pari
> 0d6244ed53 Trac #25702: Upgrade to matplotlib 2.2.2 and make its new 
> dependency kiwisolver a standard package
> 031dfcbea1 Trac #26072: py3: fix intlist.pyx doctest
> d4556754e5 Trac #26045: py3 some fixes in root_systems
> a1a2333832 Trac #26044: Delete unused "six" from mac app
> f3cd2c6cf2 Trac #26033: Upgrade to Sphinx 1.7.6
> 549e34cb29 Trac #26010: Split database_pari
> 1a84ef7586 Trac #26005: bug in local_analytic_interpolation
> e6139d3f04 Trac #26004: LatticePoset: Faster is_sectionally_complemeted
> 2e71b449dc Trac #25990: Precision issue in conversion
> 2587e46097 Trac #25714: Installing GAP package nq
> 0d026c9fec Trac #20867: SU(3,3) does not inherit from 
> FinitelyGeneratedMatrixGroup_gap
> c6fa6dac1b Trac #26066: Assertion error in mac_lane_step starting from 
> non-Gauss valuations
> d2ba76c10c Trac #26064: py3: hash for SymbolicConstantsSubring
> 3860c306ce Trac #26063: py3: hash for Hamming code
> 12016d8582 Trac #26062: py3: hash for shifted prime tableaux
> 6710f309e4 Trac #26061: py3: hash and richcmp for crystals of alcove paths
> 2348d608b5 Trac #26058: py3: hash for Bruhat Tits etc
> 2815c993d3 Trac #26057: add some missing doctests in combinat
> b34cbfdaf1 Trac #26054: cleanup misc/misc.py
> 7b609d294e Trac #26053: implement Dedekind psi function
> 1786b8739a Trac #26047: pyflakes cleanup in species
> 50c5e779c1 Trac #26046: py3: fixing oeis
> 72a244e117 Trac #26043: py3: fix MethodType(meth, obj, cls)
> d7c91a4c85 Trac #26040: using iterators inside some "all, any, tuple" in pyx 
> files
> 5f7b7108d8 Trac #26035: py3: some details in polyhedron
> 025396e5c7 Trac #26034: fixing invalid escape sequences in rings (final)
> 5bdd521033 Trac #26032: fixing invalid escape sequences in matroids (final)
> 19ab7d2765 Trac #26031: fixing invalid escape sequences in groups (final)
> ec853d5281 Trac #26030: fixing invalid escape sequences in combinat (final)
> d55e21ebf8 Trac #23437: Loading and saving BinaryMatroids can cause infinite 
> loops
> 3b2be7589e Trac #25907: Better handling of memory limits on tests
> a67d3311f3 Trac #26028: Bug-Fixes and improvements with respect to the 
> bilinear invariant form of classical matrix groups
> 71a98b0fea Trac #26019: py3: fixes to sage.rings.polynomial.real_roots
> 5b83229cf4 Trac #25965: Fixes to Dokchitser L-function script, including 
> evaluation at 0
> d38b639abe Trac #25953: Add method for visualizing order ideals
> 90b3d86408 Trac #25950: py3: use WithEqualityById in implementation of 
> ChowGroup_class
> 35a80b5be2 Trac #25948: py3: a few more miscellaneous dict iterator 
> (dict.keys, dict.values) fixes
> 5e3de89a76 Trac #25946: py3: fixes for sage.schemes.hyperelliptic_curves
> 3e61e16691 Trac #25928: Implement Permutation Pattern Posets
> 8094d182b8 Trac #25840: py3: towards pdf-docbuild. some care for automethod
> 951f8f4d60 Trac #25806: Pass --no-readline to R
> cd47f1bf72 Trac #25768: py3: fix in link.py
> 0be709e462 Trac #25642: wrong cardinality in PartitionDiagrams
> 40c55f545d Trac #25462: make SetPartition much faster
> a677bc5a99 Trac #24735:

Re: [sage-release] Sage 8.4.beta2 released

[Erik Bray]

On Tue, Aug 28, 2018 at 12:10 PM Jeroen Demeyer  wrote:
>
> On 2018-08-28 11:34, Erik Bray wrote:
> > I did get one strange failure I have never seen before:
> >
> > sage -t --long --warn-long 304.2 src/sage/parallel/map_reduce.py
> > **
> > File "src/sage/parallel/map_reduce.py", line 281, in 
> > sage.parallel.map_reduce
> > Failed example:
> >  st = pstats.Stats(prof+'0')
> > Expected nothing
> > Got:
> >  Exception AssertionError: AssertionError('TripleDictEraser: key
> > match but no weakref match',) in
> > 
> > ignored
> > **
>
> Is it reproducible?

Not in any obvious way.  I could try re-running make ptestlong and see
if it happens again.  I haven't looked any closer to see where this
might come from.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta2 released

[Erik Bray]

On Tue, Aug 28, 2018 at 1:57 PM Erik Bray  wrote:
>
> On Tue, Aug 28, 2018 at 12:10 PM Jeroen Demeyer  wrote:
> >
> > On 2018-08-28 11:34, Erik Bray wrote:
> > > I did get one strange failure I have never seen before:
> > >
> > > sage -t --long --warn-long 304.2 src/sage/parallel/map_reduce.py
> > > **
> > > File "src/sage/parallel/map_reduce.py", line 281, in 
> > > sage.parallel.map_reduce
> > > Failed example:
> > >  st = pstats.Stats(prof+'0')
> > > Expected nothing
> > > Got:
> > >  Exception AssertionError: AssertionError('TripleDictEraser: key
> > > match but no weakref match',) in
> > > 
> > > ignored
> > > **
> >
> > Is it reproducible?
>
> Not in any obvious way.  I could try re-running make ptestlong and see
> if it happens again.  I haven't looked any closer to see where this
> might come from.

I re-ran make ptestlong with the same number of processes
(SAGE_NUM_THREADS=2 in this case) and all tests passed; this exception
did not occur anywhere.  So it must be quite random and/or rare,
whatever it is.  I don't know what TripleDictEraser is.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.4.beta3 released

[Erik Bray]

`make ptestlong` still passing without a hitch on Cygwin.  Thanks for
the update!
On Mon, Sep 3, 2018 at 2:01 PM Eric Gourgoulhon  wrote:
>
> On Ubuntu 18.04 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull 
> develop, parallel (-j16) build OK and all tests passed (from make ptestlong).
>
> Eric.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta4 released

[Erik Bray]

On Fri, Sep 7, 2018 at 1:24 AM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html

On Cygwin `make ptestlong` with 4 processes gave me a few random
failures.  I have a lot of browser tabs open so I'm getting a lot of
spurious

 ***   Warning: not enough memory, new PARI stack 8545042432

warnings as the cause for most of the random failures.  I really need
to figure out how to disable that message for good.

But I also got this failure again:

sage -t --long --warn-long 168.0 src/sage/parallel/map_reduce.py
**
File "src/sage/parallel/map_reduce.py", line 281, in
sage.parallel.map_reduce
Failed example:
st = pstats.Stats(prof+'0')
Expected nothing
Got:
Exception AssertionError: AssertionError('TripleDictEraser:
key match but no weakref match',) in

ignored
**
1 item had failures:
   1 of  48 in sage.parallel.map_reduce
[300 tests, 1 failure, 68.01 s]

Last time I saw this I could never manage to reproduce this, but there
it is again in the exact same place before, so it's at least not
completely random.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta4 released

[Erik Bray]

On Tue, Sep 11, 2018 at 11:08 AM Erik Bray  wrote:
>
> On Fri, Sep 7, 2018 at 1:24 AM Volker Braun  wrote:
> >
> > As always, you can get the latest beta version from the "develop" git 
> > branch. Alternatively, the self-contained source tarball is at 
> > http://www.sagemath.org/download-latest.html
>
> On Cygwin `make ptestlong` with 4 processes gave me a few random
> failures.  I have a lot of browser tabs open so I'm getting a lot of
> spurious
>
>  ***   Warning: not enough memory, new PARI stack 8545042432
>
> warnings as the cause for most of the random failures.  I really need
> to figure out how to disable that message for good.
>
> But I also got this failure again:
>
> sage -t --long --warn-long 168.0 src/sage/parallel/map_reduce.py
> **
> File "src/sage/parallel/map_reduce.py", line 281, in
> sage.parallel.map_reduce
> Failed example:
> st = pstats.Stats(prof+'0')
> Expected nothing
> Got:
> Exception AssertionError: AssertionError('TripleDictEraser:
> key match but no weakref match',) in
> 
> ignored
> **
> 1 item had failures:
>1 of  48 in sage.parallel.map_reduce
> [300 tests, 1 failure, 68.01 s]
>
> Last time I saw this I could never manage to reproduce this, but there
> it is again in the exact same place before, so it's at least not
> completely random.

Well, I can reproduce this reliably now by running

SAGE_NUM_THREADS=2 ./sage -t --long src/sage/parallel/map_reduce.py

without the SAGE_NUM_THREADS=2 it doesn't happen.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta4 released

[Erik Bray]

On Tue, Sep 11, 2018 at 11:51 AM Jeroen Demeyer  wrote:
>
> On 2018-09-11 11:08, Erik Bray wrote:
> > On Cygwin `make ptestlong` with 4 processes gave me a few random
> > failures.  I have a lot of browser tabs open so I'm getting a lot of
> > spurious
> >
> >   ***   Warning: not enough memory, new PARI stack 8545042432
> >
> > warnings as the cause for most of the random failures.
>
> Can you give an example of such a failure? Does it happen only after
> forking? And how much RAM does that machine have?

I'll have to look into the specifics later.  This is on my laptop
which ha 32GB of RAM currently at roughly 50% utilization, though that
obviously goes up when running parallel tests.

If I recall correctly it's not really a problem that the warning is
occurring; I just don't want it to be *displayed*, especially not
while running the tests.  At least not in general.  It's not very
important.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta4 released

[Erik Bray]

On Tue, Sep 11, 2018 at 11:34 AM Erik Bray  wrote:
>
> On Tue, Sep 11, 2018 at 11:08 AM Erik Bray  wrote:
> >
> > On Fri, Sep 7, 2018 at 1:24 AM Volker Braun  wrote:
> > >
> > > As always, you can get the latest beta version from the "develop" git 
> > > branch. Alternatively, the self-contained source tarball is at 
> > > http://www.sagemath.org/download-latest.html
> >
> > On Cygwin `make ptestlong` with 4 processes gave me a few random
> > failures.  I have a lot of browser tabs open so I'm getting a lot of
> > spurious
> >
> >  ***   Warning: not enough memory, new PARI stack 8545042432
> >
> > warnings as the cause for most of the random failures.  I really need
> > to figure out how to disable that message for good.
> >
> > But I also got this failure again:
> >
> > sage -t --long --warn-long 168.0 src/sage/parallel/map_reduce.py
> > **
> > File "src/sage/parallel/map_reduce.py", line 281, in
> > sage.parallel.map_reduce
> > Failed example:
> > st = pstats.Stats(prof+'0')
> > Expected nothing
> > Got:
> > Exception AssertionError: AssertionError('TripleDictEraser:
> > key match but no weakref match',) in
> > 
> > ignored
> > **
> > 1 item had failures:
> >1 of  48 in sage.parallel.map_reduce
> > [300 tests, 1 failure, 68.01 s]
> >
> > Last time I saw this I could never manage to reproduce this, but there
> > it is again in the exact same place before, so it's at least not
> > completely random.
>
> Well, I can reproduce this reliably now by running
>
> SAGE_NUM_THREADS=2 ./sage -t --long src/sage/parallel/map_reduce.py
>
> without the SAGE_NUM_THREADS=2 it doesn't happen.

I think it might be something similar to this issue:
https://bugs.python.org/issue14548  The exact details aren't clear to
me yet, but if you fork in the middle of a garbage collection cycle
(quite likely in the sage.parallel.map_reduce module which is why this
happens to be appearing there), I suppose you could end up in some
fork-unsafe state.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta4 released

[Erik Bray]

On Tue, Sep 11, 2018 at 2:56 PM Jeroen Demeyer  wrote:
>
> On 2018-09-11 12:29, Erik Bray wrote:
> > It's not very important.
>
> It's not very important for Sage.

That's what I mean.  If I can just turn it off in Sage that would be best.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta5 released

[Erik Bray]

On Mon, Sep 17, 2018 at 5:04 AM Andy Howell  wrote:
>
> Steven,
>
> Thanks for confirming I'm an idiot:) I did have a test.py in there. Sorry for 
> the noise. Re-running the tests to make sure, but its almost certainly my 
> fault.

In fairness, that test is poorly written if merely having a file
called test.py in your SAGE_ROOT can break it.  I think I've been
bitten by that one as well.  It's not your fault.

> On 09/16/2018 09:42 PM, Steven Trogdon wrote:
>
> Just guessing, but do you by chance have the file 'test.py' in SAGE_ROOT? I 
> think that's where it's looking. If so, remove it and repeat the tests.
>
> On Sunday, September 16, 2018 at 3:38:44 PM UTC-5, Andy Howell wrote:
>>
>> I'm getting two tests failing on Ubuntu 18.04.1 LTS
>>
>> sage -t --long --warn-long 39.4 src/sage/repl/attach.py  # 7 doctests failed
>> sage -t --long --warn-long 39.4 src/sage/repl/load.py  # 1 doctest failed
>>
>> I did an incremental build and the test failed. I did a distclean,
>> rebuild, and ran ptestlong again. It still fails.
>>
>> Log for failed tests below.
>>
>> Regards,
>>
>> Andy
>>
>>
>> sage -t --long --warn-long 39.4 src/sage/repl/attach.py
>> **
>> File "src/sage/repl/attach.py", line 171, in
>> sage.repl.attach.load_attach_path
>> Failed example:
>> attach('test.py')
>> Expected:
>> Traceback (most recent call last):
>> ...
>> IOError: did not find file 'test.py' to load or attach
>> Got:
>> 
>> Traceback (most recent call last):
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 659, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 1070, in compile_and_execute
>> exec(compiled, globs)
>>   File "", line 1, in
>> 
>> attach('test.py')
>>   File "sage/misc/lazy_import.pyx", line 354, in
>> sage.misc.lazy_import.LazyImport.__call__
>> (build/cythonized/sage/misc/lazy_import.c:3759)
>> return self.get_object()(*args, **kwds)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/repl/attach.py",
>> line 349, in attach
>> load(filename, globals(), attach=True)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/repl/load.py",
>> line 243, in load
>> exec(code, globals)
>>   File "./test.py", line 4, in 
>> h=e^-x
>> NameError: name 'e' is not defined
>> **
>> File "src/sage/repl/attach.py", line 176, in
>> sage.repl.attach.load_attach_path
>> Failed example:
>> attach('test.py')
>> Exception raised:
>> Traceback (most recent call last):
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 659, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 1070, in compile_and_execute
>> exec(compiled, globs)
>>   File "", line 1, in
>> 
>> attach('test.py')
>>   File "sage/misc/lazy_import.pyx", line 354, in
>> sage.misc.lazy_import.LazyImport.__call__
>> (build/cythonized/sage/misc/lazy_import.c:3759)
>> return self.get_object()(*args, **kwds)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/repl/attach.py",
>> line 349, in attach
>> load(filename, globals(), attach=True)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/repl/load.py",
>> line 243, in load
>> exec(code, globals)
>>   File "./test.py", line 4, in 
>> h=e^-x
>> NameError: name 'e' is not defined
>> **
>> File "src/sage/repl/attach.py", line 178, in
>> sage.repl.attach.load_attach_path
>> Failed example:
>> attached_files() == [fullpath]
>> Expected:
>> True
>> Got:
>> False
>> **
>> File "src/sage/repl/attach.py", line 183, in
>> sage.repl.attach.load_attach_path
>> Failed example:
>> load('test.py')
>> Expected:
>> Traceback (most recent call last):
>> ...
>> IOError: did not find file 'test.py' to load or attach
>> Got:
>> 
>> Traceback (most recent call last):
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 659, in _run
>> self.compile_and_execute(example, compiler, test.globs)
>>   File
>> "/home/andy/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>> line 1070, in compile_and_execute
>> exec(compiled, globs)
>>   File "", line 1, in
>> 
>>  

Re: [sage-release] Sage 8.4.beta5 released

[Erik Bray]

On Mon, Sep 17, 2018 at 10:05 AM Eric Gourgoulhon
 wrote:
>
> Le lundi 17 septembre 2018 09:10:19 UTC+2, Daniel Krenn a écrit :
>>
>> On 2018-09-15 15:25, Volker Braun wrote:
>> > As always, you can get the latest beta version from the "develop" git
>> > branch. Alternatively, the self-contained source tarball is at
>> > http://www.sagemath.org/download-latest.html
>>
>> I get an error quite early: Fresh git clone and then make immediately fails:
>>
>> dakrenn@nops:/opt/sage/8.4.beta5$ make
>> make build/make/Makefile --stop
>> make[1]: Entering directory '/opt/sage/8.4.beta5'
>> ./bootstrap -d
>> make[2]: Entering directory '/opt/sage/8.4.beta5'
>> rm -rf config configure build/make/Makefile-auto.in
>> make[2]: Leaving directory '/opt/sage/8.4.beta5'
>> ./bootstrap: line 30: aclocal: command not found
>>
>
> I had exactly the same issue with Ubuntu 18.04.
> I installed the package automake (and its dependency autotools-dev) to solve 
> it (build is proceeding smoothly now).
> Since automake was not necessary to build Sage 8.4.beta3, I guess there has 
> been some recent change in the build system.

I opened https://trac.sagemath.org/ticket/26298 for this.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta6 released

[Erik Bray]

On Sat, Sep 22, 2018 at 12:36 PM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> b84538eeea (tag: 8.4.beta6, trac/develop) Updated SageMath version to 
> 8.4.beta6
> 85002aa388 Trac #26320: a small set of typos
> 74d81fdd15 Trac #26283: py3: minor fixes and refactoring in 
> sage.schemes.affine
> bd00b027e7 Trac #25694: py3: miscellaneous test fixes in sage.structure
> 1f291522a6 Trac #26331: change aut method of partition
> 33be3b7ce9 Trac #26328: py3: tiny fix in species
> b271831b9d Trac #26324: py3: some care for map
> 0f3fa0785a Trac #26322: py3: fixing doctests in subword complex and yang 
> baxter graph
> 9dc2b214fa Trac #26313: py3: hash for affine space
> 938e96bf2f Trac #26307: compute DOL languages
> c037f7f902 Trac #26125: 3 other internet doctests failing in oeis.py
> 2876fa2f26 Trac #26079: Quotients of finite dimensional Lie algebras
> 2ac6414871 Trac #25537: sage -rst2ipynb should provide a usefull message if 
> rst2ipynb is not installed
> 73f85e46fc Trac #25148: Implement ordered multiset partitions
> 3ea475e0fc Trac #24955: py3: miscellaneous fixes related to __func__
> 384a928105 Trac #12560: Artin-Hasse exponential
> 995372e5f5 Trac #26308: py3: Fix display of empty `Set`
> d41260eec1 Trac #26316: py3: doctests for commutative_dga.py
> 17610094a6 Trac #26312: py3: misc minor fixes for 
> sage.misc.rest_index_of_methods
> 4f4c5ca734 Trac #6392: modular abelian quotient -- something goes wrong
> 96b4ab8ca9 Trac #26310: py3: fix doctests in docs/
> 1e48ad551e Trac #26309: py3: fixing doctest in programming tutorials
> c7877f52e5 Trac #25378: I/O operation on closed file when sage -t 
> --optional=sage,external --logfile is_provided.log
> b34b14d172 Trac #20773: MixedIntegerLinearProgram.new_variable could 
> optionally take a "static" list of component indices
> 9ac1f78509 Trac #20145: Hilbert series bug
> b5aa8a2d03 Trac #26305: bug in degree_of_semi_regularity of multivariate 
> polynomial ideal
> 4360ffdccf Trac #26296: removed deprecated N method in element.pyx
> 6384388128 Trac #26275: py3: Fix categories/regular_supercrystals.py for 
> python3
> a34da77352 Trac #26255: coxeter_matrix of ReflectionGroup does not agree with 
> the relations
> 29b9f68e33 Trac #26243: Provide Hilbert series implementation beyond 
> Singular's limitations
> 413d3ec997 Trac #26280: py3: more trivial fixes to 
> sage.rings.polynomial.polydict
> d9a931dbc6 Trac #26199: LatticePoset: Faster is_cosectionally_complemeted
> 447a9784d9 Trac #26048: Implement the universal Askey-Wilson algebra
> 17fdba49d8 Trac #25090: Upgrade Normaliz version to 3.6.3 and PyNormaliz to 
> 1.19
> 026394faee Trac #4942: find_root() is broken when interval borders cannot be 
> evaluated
> b5b74db6f2 Trac #26259: cleanup magma interface
> 15c2932e12 Trac #25910: Add the product of chains to the catalog of posets
> 4c04757a27 Trac #26295: py3: fix doctests in tensor/
> 0c9b51f0af Trac #26294: py3: fix doctests in monoids/
> 1051ef2919 Trac #26117: Upgrade to sympy 1.2
> b54d72dc76 Trac #26290: some conversion from NOTES: to .. NOTE::
> ca26fcca0f (tag: 8.4.beta5, sagemath/develop) Updated SageMath version to 
> 8.4.beta5

Incremental `make ptestlong` passed with no problems on Cygwin.
Building from scratch may have a new-found blocker in the form of
https://trac.sagemath.org/ticket/25057  This was never a blocker for
me before but it appears it might be on more recent versions of Cygwin
or, possibly, just on systems that don't already have a primed ccache.
It's not exactly clear to me why the problem only recently started
appearing.  Fortunately the fix, if I'm correct, should be simple and
I'm testing it now.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.beta7 released

[Erik Bray]

Looks fine on Ubuntu 14.04 machine.

Sometimes when I run the tests I get failures like:

sage -t --long src/sage/combinat/cluster_algebra_quiver/quiver.py
**
File "src/sage/combinat/cluster_algebra_quiver/quiver.py", line 172,
in sage.combinat.cluster_algebra_quiver.quiver.ClusterQuiver
Failed example:
Q.mutation_type()
Exception raised:
Traceback (most recent call last):
  File 
"src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 659, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 1070, in compile_and_execute
exec(compiled, globs)
  File "", line
1, in 
Q.mutation_type()
  File 
"src/sagemath/sage/local/lib/python2.7/site-packages/sage/combinat/cluster_algebra_quiver/quiver.py",
line 1009, in mutation_type
mut_type_part = _mutation_type_from_data(
dg_component.order(), dig6, compute_if_necessary=False )
  File 
"src/sagemath/sage/local/lib/python2.7/site-packages/sage/combinat/cluster_algebra_quiver/mutation_type.py",
line 1313, in _mutation_type_from_data
data = load_data(n)
  File "sage/misc/cachefunc.pyx", line 1005, in
sage.misc.cachefunc.CachedFunction.__call__
(build/cythonized/sage/misc/cachefunc.c:6302)
w = self.f(*args, **kwds)
  File 
"src/sagemath/sage/local/lib/python2.7/site-packages/sage/combinat/cluster_algebra_quiver/mutation_type.py",
line 1288, in load_data
data_new = cPickle.load(fobj)
ValueError: unsupported pickle protocol: 3

This is because I'm using the same machine to build and test Python 3,
and that code is caching some computations as pickles in .sage/; so
when I run them on Python 3 it ends up with some Python 3 pickles in
.sage.

I believe these tests ought to be fixed to not use the user's real
.sage since that's hard to control for.  But that's a minor issue and
not particular to this release.  It just gets me almost every time :)
On Mon, Oct 1, 2018 at 12:55 AM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> a1bfef8cf3 (tag: 8.4.beta7, trac/develop) Updated SageMath version to 
> 8.4.beta7
> cbd85e1df0 Trac #26353: MR1: Remove special case for Cygwin for BLAS 
> detection when installing fflas_ffpack
> a090fd23c8 Trac #25913: Allow input as packed words for Hopf algebra WQSym
> 4048cdea8c Trac #26352: Lie algebra quotients are incorrect for some basis 
> orders
> 958b066cf6 Trac #26232: enhance pari conversion of elliptic curves over 
> number field
> dfa5859869 Trac #25435: Global function fields: orders and ideals
> cf373c1968 Trac #12567: Implement p-adic n-th roots
> 83f13e288a Trac #26350: Add citations to polymake papers
> e643ef4bf4 Trac #26346: py3: a bit of work in src/doc
> fdfbfef6ab Trac #26347: clean deprecation warning in doctests for paths.py + 
> animate.py
> 15dbacc580 Trac #26342: Improve triconnectivity algorithm: avoid recursive 
> calls
> 24442c1091 Trac #25057: Building ecl-16.1.2 fails on some Cygwin versions
> 19cff46d56 Trac #24589: Pickling matrices over GF(2) does not preserve their 
> immutability
> 039b874739 Trac #26080: The Baker-Campbell-Hausdorff formula for nilpotent 
> Lie algebras
> d72db87107 Trac #26016: py3: miscellaneous fixes and cleanup to sage.sandpiles
> 02e5631e78 Trac #26011: Copying package files is really slow
> 6e84381666 Trac #26341: py3: misc open(...) -> with open(...) fixes
> bbc97631c5 Trac #26325: Upgrade nose to 1.3.7
> d8efd6a554 Trac #26323: small update of faq_usage
> cabf20b1dd Trac #26299: py3: use repr for floats in plot3d file format outputs
> 9ad5cf0c99 Trac #26335: PicoSAT solver
> df44cb2c3c Trac #26334: Package pycosat
> a74f7590ad Trac #26329: Allow xor clause in DIMACS files (format extended by 
> cryptominisat)
> 957af679a7 Trac #25395: Support for binary quintics in invariant_theory
> e2e3f3f9bd Trac #26338: Fix documentation formatting in modular symbol space
> 7c8d581c7c Trac #26336: Fix latex typos in sfa.py
> 614c0368ec Trac #26227: Make search_doc independent of sage_setup
> b84538eeea (tag: 8.4.beta6) Updated SageMath version to 8.4.beta6
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, s

Re: [sage-release] Re: Sage 8.4.rc0 released

[Erik Bray]

On Mon, Oct 8, 2018 at 7:53 AM Jeroen Demeyer  wrote:
>
> On 2018-10-07 21:32, Volker Braun wrote:
> > I've seen this sometimes when running out of memory (docbuild gets stuck
> > instead of erroring out)
>
> This is just general suckiness of multiprocessing.Pool
>
> I have a long-standing plan to extract the multiprocess code from the
> doctesting framework and use that in other place like the docbuilder too.

Hahah, same.  I had a prototype for this working more than a year ago
but I got frustrated by some tiny bug somewhere and never went back to
it.  I should probably try again and start a bit simpler...  It's not
too hard to take the already existing code almost verbatim and just
replace the body of the Worker.run method with something more generic.
However, I was also trying to support the full concurrent.futures API
(but extended to include the doctest framework's support for stdout
capture from subprocesses), and that's where things got hairy.

I should probably dig up that code and take another stab at it...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.4.rc0 released

[Erik Bray]

On Sun, Oct 7, 2018 at 10:43 AM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> 90e17493c0 (tag: 8.4.rc0, trac/develop) Updated SageMath version to 8.4.rc0
> d2376f6767 Trac #26404: py3: fix doctest in libgap_wrapper
> 16485ae125 Trac #26399: py3: fix doctest in yangian
> ac63eaf0a7 Trac #26301: Python 3 bug in zipfile
> 10b706e329 Trac #25891: Implementing generators for Hamming graphs, Egawa 
> graphs and Cai-Furer-Immerman graphs
> 0225ecc0d9 Trac #26413: absolute_import for 
> src/sage/libs/linbox/linbox_flint_interface.pyx
> c059cda3ac Trac #26402: Set language_level for cython() command
> 68aae1ead0 Trac #26401: py3: fix doctests in stats
> b43b4d2de5 Trac #26285: Avoid comparison of vertex labels in MIP (Step 4)
> cbae347618 Trac #25776: Better printing for the genus symbol
> 5bcc887e22 Trac #25477: possibly improve the iterator for PermutationGroups
> 98878998d4 Trac #24852: Fix bytes/str in sage.data_structures.bitset
> e1b34536a4 Trac #26397: py3: allow Python 3 bytes to be multiplied by Sage 
> Integers
> 2232c43817 Trac #26321: py3: hodgepodge of (mostly) trivial doctest fixes
> c818b8b2a9 Trac #22050: Complete graph on 2 vertices doesn't show any edges
> a44cb00abc Trac #26398: py3: fix doctest in sboxes
> 57ed1d4350 Trac #26390: py3: some changes in misc
> 0a68468a62 Trac #26378: Bugs in Mass formula for quadratic forms
> 1e4eff82a6 Trac #26344: Nilpotent Lie groups
> c22cdee6a7 Trac #26284: Avoid comparison of vertex labels in MIP (Step 3)
> dae825b2f7 Trac #26282: Avoid comparison of vertex labels in MIP (Step 2)
> 14f6a6ea15 Trac #26106: Remove duplicated code in method `tkz_picture`
> 23639d4ed3 Trac #26382: py3: sorting some doctests in AnalyticType
> 629e3f612e Trac #26395: remove deprecated adams operation
> 263d791ac3 Trac #26394: Remove test for deprecated pari.bernvec
> 6b3bfd660a Trac #26393: remove deprecated code in continued fractions
> 84b32c757e Trac #26392: remove deprecated view in tensor
> 63bed9d31a Trac #26386: get rid of CombinatorialClass in non-symmetric 
> MacDonald
> a57eb8e1e5 Trac #26385: delete MultichooseNK
> fa7caa1860 Trac #26384: cleanup non-decreasing parking functions
> 15d4fe7eb0 Trac #26380: py3: some fixes in plot3d
> 314afb66ea Trac #26370: Move invariant theory to seperate subfolder
> 12a9bfb3d4 Trac #26369: Improve triconnectivity algorithm: some cythonization
> 980c699915 Trac #26289: pyflakes in generic_graph.py
> 299fee6442 Trac #26274: Avoid comparison of vertex labels (Step 1)
> 313b702456 Trac #25995: update installation guide
> 2c431e1244 Trac #25682: Add access methods to the genus.
> 5095b27d91 Trac #26383: Include missing patch for openblas from #24669
> 3b88086008 Trac #26381: py3: some doctests fixes in graphs
> 7244ea7038 Trac #26376: py3: fix a bunch of syntax errors
> e20d2f572d Trac #26371: py3: wrapping some map(...) in manifolds
> 46aee00b2a Trac #25134: Derivation and twisted derivations over rings
> 6f193d8e49 Trac #26345: Py3 : Fix few str/bytes problems in sage/combinat
> 4ccf7a2cf3 Trac #26377: fixing invalid escape sequences (again)
> adcd822e6a Trac #26374: py3: sort one doctest in elliptic curves
> be0a46dd7e Trac #26373: py3: some fixes in strongly regular graphs
> d28d0539b3 Trac #26372: py3: fix some bad range (again and again)
> c37cf3fb0f Trac #26354: Pickling morphisms is broken
> 75b56ee702 Trac #26298: Add build/bin to path in bootstrap script
> 7c55d1c5fd Trac #26365: Library of polytopes should allow specifying 
> backend=... (follow-up)
> 5d045236b4 Trac #26362: py3: some care for islice in words
> 7e1685679f Trac #25911: Increasing tableau class
> f3ff222f71 Trac #22701: Setting up a Polyhedron from both Vrep and Hrep - for 
> backend='field'
> 19ba603f45 Trac #22575: Fix Polyhedron.base_extend so it does not ignore the 
> backend parameter
> 5dc3fd2a5c Trac #26050: Upgrade zn_poly
> a1bfef8cf3 (tag: 8.4.beta7) Updated SageMath version to 8.4.beta7

On Cygwin I manually did a `./sage -f openblas` since I had not
updated the patch level in #26383 (in retrospect perhaps it would have
been good to, but I didn't want to force a rebuild of openblas on all
other platforms).

Then I did an incremental `make ptestlong` and got one failure:

sage -t --long --warn-long 164.4 src/sage/repl/configuration.py
**
File "src/sage/repl/configuration.py", line 14, in sage.repl.configuration
Failed example:
'sage: [False, True]' in output
Expected:
True
Got:
False
**
1 item had failures:
   1 of   5 in sage.repl.configuration
[18 tests, 1 failure, 30.89 s]

However, this is a random fail I have known about for a long time:
https://trac.sagemath.org/ticket/23087  Though I don't recall seeing
it much recently.  Perhaps I'll

Re: [sage-release] Sage 8.5.beta1 released

[Erik Bray]

Any thoughts on the release schedule, such that it is?

I thought having the rough October 1st guideline for the last release
to be helpful.  Although we ended up cutting off changes a little
later than that (and it would have been nice to have an updated
projection as the October 1st date came nearer) it still helped me
make sure most of my top priorities for the release and blockers were
addressed.

Thanks,
E
On Sat, Oct 27, 2018 at 4:18 PM Volker Braun  wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
>
> 1a64da2382 (tag: 8.5.beta1) Updated SageMath version to 8.5.beta1
> 73b3b40813 Trac #26555: remove a deprecated method in matrix_space
> a377362574 Trac #26554: improve boost_graph.pyx
> 8edd85c19f Trac #26553: remove deprecated incomplete_gamma
> ff8372f04f Trac #26543: py3: fix doctests in sat/
> 57d4745eab Trac #26506: clean cliquer.pyx
> d3033f4682 Trac #25936: Improvements to integrated curves and geodesics on 
> manifolds
> 2c412680c9 Trac #26499: sagenb 1.1.0
> 022c7514fc Trac #26479: padic printer does not support latex names
> c8b0ab2922 Trac #26176: SageKernelSpec doctests fail in non-standard setups
> 6d6c459c6b Trac #26174: Upgrade jupyter notebook to 5.7.0
> e23129c018 Trac #26547: clean spanning_tree.pyx
> b9a4e21c02 Trac #26531: avoid using .vertices() in asteroidal_triples
> dad77b714b Trac #26514: clean centrality.pyx
> dbfe310d99 Trac #26505: clean and improve convexity_properties.pyx
> 57aa129a6f Trac #26446: clean lovasz_theta, isgci, independent_set
> add605fe7f Trac #26542: py3: fix some doctests in Cartan types
> 7f9c51da14 Trac #26541: py3: fix doctests in cachefunc.pyx
> ec0eac7f26 Trac #26540: py3: fixing some doctests in combinat and structure
> 6cb3293f7e Trac #26539: py3: fix doctests in power series
> 46496f1567 Trac #26536: py3: fix doctest in the file kraus.py
> ee49e43dac Trac #26535: py3: fix doctests in Hillman-Grassl file
> 1b62dfecd1 Trac #26534: avoid using .vertices() in weakly_chordal.pyx
> d21a4743c2 Trac #26533: clean trees.pyx
> 9c37dd82a3 Trac #26530: cleanup of the category of Coxeter groups
> cf6c751b4b Trac #26529: py3 fix elliptic curve L-series
> 960b4b705f Trac #26528: avoid using .vertices() in comparability, 
> hyperbolicity and distances_all_pairs
> fff55fd70f Trac #26525: py3 fix doctest in btquotient
> 4bc7c2c4a6 Trac #26524: py3: minor fix in misc/misc
> 334f51ecdf Trac #26515: clean bipartite_graph.py
> 37dc473c50 Trac #26480: clean graph_latex.py
> 965f0e739d Trac #26478: clean graph_plot_js.py, graph_list.py and 
> graph_input.py
> aede35877f Trac #26468: Py3: Some fixes in combinat/finite_state_machine.py
> 2eebc670e3 Trac #25609: have libgap permutation to sage use permutation 
> instead of permutation group element
> 0fc1b41305 Trac #26523: fix one doctest in hecke triangle group
> c709eed5d1 Trac #26521: fix invalid escape sequences in sboxes
> f27b6b54b3 Trac #26519: py3: care for islice
> a19aca951f Trac #26518: py3: fix for zip in nilpotent Lie groups
> ac26f85a45 Trac #26517: py3: some details about map and filter
> cb0a16fde8 Trac #26507: Remove \mathbb in the documentation
> 3955883aff Trac #26491: Maximum recursion depth exceeded when dumping a large 
> Finite State Machines
> 35c6974676 Trac #26429: py3: fix some doctests in game_theory
> 34502f45df Trac #26314: py3: Fix interfaces module for python3
> 4a533c5e95 Trac #26459: remove deprecated stuff in sloane.py
> 30bfdb5347 Trac #26454: Do not check for random output of cusps_nf.py
> a0756f9806 Trac #26445: some work on doc of Dyck path
> aee7a8eb64 Trac #26438: clean orientations.py
> 9808037f68 Trac #26422: some details in the master reference file
> 9c0ef39fe1 Trac #26416: Improve implementation of 
> sage.databases.cremona.split_code
> a0a5f5992b (tag: 8.5.beta0) Updated SageMath version to 8.5.beta0
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-release+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.5.beta1 released

[Erik Bray]

On Mon, Oct 29, 2018 at 1:25 PM Eric Gourgoulhon  wrote:
>
> Le lundi 29 octobre 2018 13:18:11 UTC+1, Eric Gourgoulhon a écrit :
>>
>> I've noticed something new in this release, certainly introduced by
>> 6d6c459c6b Trac #26174: Upgrade jupyter notebook to 5.7.0
>> The menus of the Jupyter notebook are now (partially) in French. This 
>> happens with both Firefox and Chromium. I guess this is because in the 
>> locale of my system (Ubuntu 18.04), I have
>> LANG=fr_FR.UTF-8
>> Is it possible to restore the English menus without changing the locale?
>
>
> In particular, all input cells have now
> Entrée [...]
> instead of
> In [...]
> which is awkward...
> (the output cells have still Out  [...]).

Something like that would almost certainly be a Jupyter issue I think.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.5.beta3 released

[Erik Bray]

On Mon, Nov 12, 2018 at 10:51 AM Eric Gourgoulhon
 wrote:
>
> Le lundi 12 novembre 2018 08:45:59 UTC+1, fchap...@gmail.com a écrit :
>>
>> This seems to break almost all the patchbots. Problem building the sagenb 
>> doc, probably.
>
>
> Confirmed: incremental build from Sage 8.5.beta2 yields:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> * package: sagenb-1.1.1
>   log file: /home/eric/sage/develop2/logs/pkgs/sagenb-1.1.1.log
>   build directory: 
> /home/eric/sage/develop2/local/var/tmp/sage/build/sagenb-1.1.1
>
> sagenb-1.1.1.log contains:
>
> Exception occurred:
>   File "sage/misc/lazy_import.pyx", line 218, in 
> sage.misc.lazy_import.LazyImport._get_object 
> (build/cythonized/sage/misc/lazy_import.c:2412)
> raise RuntimeError(f"resolving lazy import {self._name} during startup")
> RuntimeError: resolving lazy import dumps during startup
> The full traceback has been saved in /tmp/sphinx-err-grvYRv.log, if you want 
> to report the issue to the developers.
>
> I am attaching both sagenb-1.1.1.log and sphinx-err-grvYRv.log.

FWIW our incremental builds on the GitLab pipeline have been having
this problem ever since 8.5.beta1, so the problem started even before
now: https://gitlab.com/sagemath/sage/-/jobs/115598440  I think there
might just be a missing dependency for the new sagenb package...

I thought the problem might just be with the gitlab builds themselves,
but it seems maybe not if others are reporting this.  The problem
started there with 8.5.beta1 (beta0 worked fine).

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.