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.

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.