Re: [sage-devel] help needed to debug a systematically killed Sage

2017-04-07 Thread Jeroen Demeyer
On 2017-04-07 20:13, Vincent Delecroix wrote: 8G should be enough!? (note that Sage used to work...) Be sure to double-check dmesg and check if there is something suspicious. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] help needed to debug a systematically killed Sage

2017-04-07 Thread Jeroen Demeyer
Another guess: a sage-cleaner getting confused and killing wrong processes. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-devel] help needed to debug a systematically killed Sage

2017-04-07 Thread Vincent Delecroix
On 07/04/2017 20:12, Jeroen Demeyer wrote: On 2017-04-07 13:34, Vincent Delecroix wrote: However, after step 2) I end up with a very broken Sage that is immediately killed with no information at all Too little memory available on your system? 8G should be enough!? (note that Sage used to

Re: [sage-devel] help needed to debug a systematically killed Sage

2017-04-07 Thread Jeroen Demeyer
On 2017-04-07 13:34, Vincent Delecroix wrote: However, after step 2) I end up with a very broken Sage that is immediately killed with no information at all Too little memory available on your system? -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] help needed to debug a systematically killed Sage

2017-04-07 Thread Vincent Delecroix
Dear all, I have trouble building Sage for the patchbot. My procedure consists just in launching the attached script. It basically 1) compile sage 2) install most optional packages except the one for which I know there are some troubles 3) launch the patchbot However, after step 2) I