I was wrong, but now I am quite sure that the issue seems to appear in 
sage-7.4.beta0.

El miércoles, 1 de febrero de 2017, 23:27:35 (UTC+1), Enrique Artal 
escribió:
>
> If I am not wrong the problem is created in sage-7.3.beta3. I can try with 
> the different patches beta2->beta3. Can anyone guess a good order to do 
> that?
>
> El sábado, 14 de enero de 2017, 19:18:32 (UTC+1), Enrique Artal escribió:
>>
>> I have installed 7.3, 7.4 and 7.5 and we use several instances of sagenb 
>> (it is for teaching and we use different addresses for different studies). 
>> With 7.3, if a user reaches the limit of CPU time, his worksheet stops and 
>> all the data in memory is lost, but quitting and opening the worksheet 
>> again causes no problem, and it does not affect other users. With 7.5, the 
>> instance of the notebook must be restarted because it does not work for any 
>> user of this instance (no problem for the other ones). 
>> Is there some documentation for the debugging technique? Is it possible 
>> to take beta releases? Enrique. 
>>
>> El sábado, 14 de enero de 2017, 11:13:37 (UTC+1), Dima Pasechnik escribió:
>>>
>>> Oh, right, this certainly has nothing to do with sagenb, what is not 
>>> stopped is sage worker that does the computation itself, right?
>>>
>>> Could it be that you updated your OS in the meantime, and if you roll 
>>> back to sage 7.3 you would still see the same behaviour?
>>>
>>> On sage's side it might be ipython update, although I am guessing.
>>>
>>> There is a debugging technique that would let you find a git commit that 
>>> caused the change you noticed, using git bisect, although this might take a 
>>> full day of work or so, just because there were few hundred commits and you 
>>> would need to run 'make build' a dozen times or so, with testing after each 
>>> rebuild...
>>>
>>>

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

Reply via email to