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

[Dima Pasechnik]

this should be fixed by https://trac.sagemath.org/ticket/23225
please review

On Monday, June 12, 2017 at 1:44:58 PM UTC+1, tsc...@ucdavis.edu wrote:
>
>
>
> On Sunday, June 11, 2017 at 11:45:57 PM UTC-5, François wrote:
>>
>> On 12/06/17 16:20, tsc...@ucdavis.edu wrote: 
>> > 
>> > Given what I see, you only get this when you set 
>> SAGE_TUNE_GF2X=full. 
>> > Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no 
>> > will work. At least it looks to me like SAGE_TUNE_GF2X is set to 
>> full 
>> > from the log, let me know if this assumption is wrong. 
>> > 
>> > I didn't set SAGE_TUNE_GF2X, but it still attempted the tuning even 
>> with 
>> > it unset. However, it built fine when I did export SAGE_TUNE_GF2X=no. 
>> > 
>>
>> There are 3 levels of tuning for gf2x in the sage spkg: 
>> no) no tuning 
>> full) full tuning 
>> *) default if unset. 
>>
>> I thought it was only happening on full. But obviously I am wrong. 
>> The fix must have exposed a further bug that was more prevalent 
>> than I thought. 
>> On my machine I have no problem doing a default tuning or a full 
>> tuning with both gcc and clang. And the test suite passes in full 
>> in all configurations. 
>>
>> But given how widespread this is turning out to be, we would be 
>> better reverting https://trac.sagemath.org/ticket/18882 and 
>> wait for the new release of gf2x. The changes on git master are 
>> big enough that cherry-picking is a difficult option, and the 
>> tuning is massively faster. 
>>
>>
> I tried reverting #18882, but it didn't seem to work. Yet, I didn't delete 
> the partial install so that might have contributed. I will try again. I 
> also looked at my old build logs and it seems that tuning is the default 
> option as far back as at least 7.6.beta2.
>
> Best,
> Travis
>
>

-- 
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.

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

[Eric Gourgoulhon]

On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + 
pull develop, parallel (-j16) build OK, but make ptestlong failed with four 
files:

sage -t --long --warn-long 51.6 src/sage/interfaces/expect.py  # 1 doctest 
failed
sage -t --long --warn-long 51.6 src/sage/repl/interpreter.py  # 3 doctests 
failed
sage -t --long --warn-long 51.6 src/sage/repl/interface_magic.py  # 3 
doctests failed
sage -t --long --warn-long 51.6 src/sage/repl/ipython_tests.py  # 4 
doctests failed

All the errors are reproductible separately;



*sage -t --long --warn-long 51.6 
src/sage/interfaces/expect.py***File
 
"src/sage/interfaces/expect.py", line 1117, in 
sage.interfaces.expect.Expect._expect_expr
Failed example:
print(sage0.eval("dummy=gp.eval('0'); alarm(1); 
gp._expect_expr('1')"))  # long time
Expected:
Control-C pressed.  Interrupting PARI/GP interpreter. Please wait a few 
seconds...
...
AlarmInterrupt:
Got:
Control-C pressed. Interrupting PARI/GP interpreter. Please wait a few 
seconds...

---
AlarmInterruptTraceback 
(most recent call last)
 in 
()
...


*sage -t --long --warn-long 51.6 
src/sage/repl/interpreter.py***
File "src/sage/repl/interpreter.py", line 77, in sage.repl.interpreter
Failed example:
shell.run_cell('1/0')
Expected:

---
ZeroDivisionError Traceback (most recent call 
last)
 in ()
> 1 Integer(1)/Integer(0)

.../src/sage/rings/integer.pyx in sage.rings.integer.Integer.__div__ 
(.../cythonized/sage/rings/integer.c:...)()
   ...if type(left) is type(right):
   ...if mpz_sgn((right).value) == 0:
-> ...  raise ZeroDivisionError("rational division by 
zero")
   ...x =  Rational.__new__(Rational)
   ...mpq_div_zz(x.value, (left).value, 
(right).value)

ZeroDivisionError: rational division by zero
Got:

---
ZeroDivisionError Traceback 
(most recent call last)
 in 
()
> 1 
Integer(1)/Integer(0)

...
**
File "src/sage/repl/interpreter.py", line 358, in 
sage.repl.interpreter.SageTestShell.run_cell
Failed example:
rc = shell.run_cell('1/0')
Expected:

---
ZeroDivisionError Traceback (most recent call 
last)
...
ZeroDivisionError: rational division by zero
Got:

---
ZeroDivisionError Traceback 
(most recent call last)
 in 
()
> 1 
Integer(1)/Integer
...
**
File "src/sage/repl/interpreter.py", line 404, in 
sage.repl.interpreter.SagePreparseTransformer
Failed example:
shell.run_cell(bad_syntax)
Expected:
  File "", line unknown
SyntaxError: Mismatched ']'

Got:
  File "", line 
unknown
SyntaxError: Mismatched ']'



*sage -t --long --warn-long 51.6 src/sage/repl/interface_magic.py*
**
File "src/sage/repl/interface_magic.py", line 214, in 
sage.repl.interface_magic.InterfaceMagic.line_magic_factory
Failed example:
shell.run_cell('%gap?')
Expected:
Docstring:
Interact with gap

The line magic %gap sends a single line to the gap interface.
...
Got:
Docstring:
Interact with gap

The line magic %gap sends a single line to the gap interface.

INPUT:
...
**
File "src/sage/repl/interface_magic.py", line 262, in 
sage.repl.interface_magic.InterfaceMagic.cell_magic_factory
Failed example:
shell.run_cell('%%gap foo\n1+1;\n')
Expected:
File "", line unknown
SyntaxError: Interface magics have no options, got "foo"

Got:
  File "", line 
unknown
SyntaxError: Interface magics 
have no options, got "foo"

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

[François Bissey]

On 12/06/17 16:20, tsc...@ucdavis.edu wrote:


Given what I see, you only get this when you set SAGE_TUNE_GF2X=full.
Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no
will work. At least it looks to me like SAGE_TUNE_GF2X is set to full
from the log, let me know if this assumption is wrong.

I didn't set SAGE_TUNE_GF2X, but it still attempted the tuning even with 
it unset. However, it built fine when I did export SAGE_TUNE_GF2X=no.




There are 3 levels of tuning for gf2x in the sage spkg:
no) no tuning
full) full tuning
*) default if unset.

I thought it was only happening on full. But obviously I am wrong.
The fix must have exposed a further bug that was more prevalent
than I thought.
On my machine I have no problem doing a default tuning or a full
tuning with both gcc and clang. And the test suite passes in full
in all configurations.

But given how widespread this is turning out to be, we would be
better reverting https://trac.sagemath.org/ticket/18882 and
wait for the new release of gf2x. The changes on git master are
big enough that cherry-picking is a difficult option, and the
tuning is massively faster.

Francois

--
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.beta10 released

[tscrim]

> Given what I see, you only get this when you set SAGE_TUNE_GF2X=full. 
> Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no 
> will work. At least it looks to me like SAGE_TUNE_GF2X is set to full 
> from the log, let me know if this assumption is wrong. 
>
> I didn't set SAGE_TUNE_GF2X, but it still attempted the tuning even with 
it unset. However, it built fine when I did export SAGE_TUNE_GF2X=no.

Thanks,
Travis

 

-- 
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.beta10 released

[François Bissey]

On 12/06/17 16:04, tsc...@ucdavis.edu wrote:


 > t seems that this happens on several machines:
 >
 > Error installing package gf2x-1.1.p2
 >
 > See for example
 >
 >

https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short




I am also getting this error on my laptop when trying to do an 
incremental upgrade from beta9.



Upstream is aware of the problem. A new release of gf2x
is getting ready that hopefully will fix the problem.
No ticket for that yet.
This started after I included a fix for bug in
https://trac.sagemath.org/ticket/18882



It may have triggered another bug down the line.
See above ticket for more info.

What is the currently workaround for getting gf2x to build? Is it 
reverting #18882?




Given what I see, you only get this when you set SAGE_TUNE_GF2X=full.
Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no
will work. At least it looks to me like SAGE_TUNE_GF2X is set to full
from the log, let me know if this assumption is wrong.

Francois

--
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.beta10 released

[tscrim]

> > t seems that this happens on several machines: 
> > 
> > Error installing package gf2x-1.1.p2 
> > 
> > See for example 
> > 
> > 
> https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short
>  
> 
>  
>
> I am also getting this error on my laptop when trying to do an incremental 
upgrade from beta9.
 

>
> Upstream is aware of the problem. A new release of gf2x 
> is getting ready that hopefully will fix the problem. 
> No ticket for that yet. 
> This started after I included a fix for bug in 
> https://trac.sagemath.org/ticket/18882 
> 
>  
> It may have triggered another bug down the line. 
> See above ticket for more info. 
>
> What is the currently workaround for getting gf2x to build? Is it 
reverting #18882?

Best,
Travis

 

-- 
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.beta10 released

[Francois Bissey]

> On 12/06/2017, at 07:10, fchapot...@gmail.com wrote:
> 
> t seems that this happens on several machines:
> 
> Error installing package gf2x-1.1.p2
> 
> See for example
> 
> https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short
> 

Upstream is aware of the problem. A new release of gf2x
is getting ready that hopefully will fix the problem.
No ticket for that yet.
This started after I included a fix for bug in 
https://trac.sagemath.org/ticket/18882
It may have triggered another bug down the line.
See above ticket for more info.

François

-- 
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.

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

[fchapoton2]

It seems that this happens on several machines:

Error installing package gf2x-1.1.p2

See for example

https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short

Frederic

Le dimanche 11 juin 2017 13:58:04 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
>
> ffc8eff Updated SageMath version to 8.0.beta10
> 71caaea Trac #23169: is_squarefree can be implemented on the base as 
> _is_squarefree_univariate_polynomial
> 554fe30 Trac #23166: Conversion from a Function Field to its underlying 
> Polynomial Ring
> fadc6fe Trac #23156: py3: no __cmp__ in sudoku
> ef6abe1 Trac #23150: py3: caring for a few cmp in modular folder
> 0db5d48 Trac #23149: py3: get rid of cmp_props
> dba1080 Trac #23148: py3: richcmp in pari ring
> c32cc6e Trac #23147: py3: little cleanup of six and unicode
> 65ef964 Trac #23142: Fix missing synchronisation upon starting gap3
> ad64e9d Trac #23140: Gauss-Legendre Integrator
> 66bee23 Trac #23137: free dendriform algebras
> cc6cec7 Trac #23133: py3: deprecate lexico comparison for complex 
> intervals field
> f3881ba Trac #23130: py3: some care for map in various places
> bea0dd6 Trac #23043: Fast p-adic logarithm
> bc61743 Trac #22685: Improve 3D plot documentation
> 117e9e3 Trac #15104: Special case modn_dense matrix operations to improve 
> performance
> b8d4f05 Trac #23146: Upgrade to MPIR 3.0 broke SAGE_FAT_BINARY=yes
> ce4848e Trac #23117: Set up embeddings for extensions created using the 
> syntax R[alg]
> 8462378 Trac #23090: Some curation in desolvers.py
> 48c940f Trac #23066: sagenb update to 1.0
> bf41596 Trac #23044: py3: tolerance for u prefix in doctests
> df3f064 Trac #22769: tensor_product fails when one of the matrices has 0 
> rows or columns
> e15ab84 Trac #22202: Warning while working with algebraic numbers
> ca740c5 Trac #18430: Bug in is_hyperbolic
> a679ccd Trac #7675: shortest_path in c_graph should have an optional flag 
> distance=False to return only the distance
> 45e989a Trac #23126: Hidden bug: matching_polynomial() for graphs without 
> edges
> 69d5da2 Trac #23124: Fix sig_on/sig_off in boost_graph.pyx
> 380655a Trac #23123: Stop using cysignals .pxi files (part 5)
> 7a39f63 Trac #23121: Stop using cysignals .pxi files (part 4)
> 6b4b358 Trac #23110: typos in polyhedron base
> 597542d Trac #23108: Add an example to expand_trig
> 2ff000a Trac #23105: py3: remove 
> 78b166b Trac #22894: Symbolic expression.is_exact()
> ed1a82c Trac #22026: Doctests: Even reals are integers
> f9974f9 Trac #20348: p-adic floating point rings
> e5589be Trac #18882: Random failure in gf2x testsuite
> 042ecb6 Trac #23103: Move richcmp stuff to new file
> a69b17d Trac #23096: New format for the package installed stamp files in 
> $SAGE_SPKG_INST
> ccc7410 Trac #23079: genus of an Elliptic Curve over a finite field
> b26b353 Trac #22908: generator of random block graph
> e0ddc65 Trac #22706: Add more conversions from giac
> 2d1a0e5 Trac #12652: update or remove experimental spkg vtk and related 
> docs
> 375e9fa Trac #23128: sage.misc.cython broken on Cygwin
> 191ce3e Trac #23122: Wrong zlib library might be loaded
> a2901ca Trac #23095: autogen/interpreters does NOT work
> 9da6672 Trac #22628: SINGULAR_SO default is incorrect of Cygwin
> d9e145d Updated SageMath version to 8.0.beta9
>
>

-- 
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.