[sage-devel] Re: Failing doctest in src/sage/rings/integer.pyx

Update: The test just takes way too much memory for a doctest, I would think. Consider the following: sage: n = prod(primes_first_n(25)) sage: _ = n.divisors() This takes a good 3 GB of RAM and it does not appear to be a memory leak (the doctest claims this to be the problem on failure). I can

[sage-devel] Re: Failing doctest in src/sage/rings/integer.pyx

Is there an option to run a patchbot with more memory as in `./sage -t --long --all -m ...'? There seems to be a general problem with `alarm` (especially when using `./sage -t`) for i in range(20): # long time try: alarm(RDF.random_element(1e-3, 0.5)) _ = n.

Re: [sage-devel] "sage -t" command line options do not work

* > 1 item had failures: > 2 of 3 in toto > [2 tests, 2 failures, 0.00 s] > -- > sage -t toto.py # 2 doctests failed > -- &

[sage-devel] "sage -t" command line options do not work

According to "sage -t --help" there is an option "--exitfirst", but it does not work (unknown option). Likewise the option "-i" does not seem to have any impact. This is annoying when one has lots of errors and wants to see the first one. I'm running sage on the develop branch on a debian (htt

Re: [sage-devel] Trac down?

Down again. Am Donnerstag, 25. April 2019 01:21:07 UTC+2 schrieb Dima Pasechnik: > > I've logged in, and see quite an overload of the machine, mainly by > cgit, 40-50 processes, taking all CPUs... > I'll reboot again, but I don't know what to do to fix this properly. > > -- Forwarded me

[sage-devel] Failing doctest in src/sage/rings/integer.pyx

I'm getting the same error as in #26002 in src/sage/rings/integer.pyx In my patchbot run https://patchbot.sagemath.org/log/0/debian/9.8/x86_64/4.9.0-8-amd64/cofio/2019-03-13%2016:31:01 this just appeared as slow, but I don't see that this test should have

[sage-devel] Re: Patchbot zancara: Disk quota exceeded

I just saw this. Wasn't subscribed back then. But I noticed that my home was full :-) This is solved now. I had to change DOT_SAGE and CCACHE_DIR, as I only have very limited amount of memory in home. Maybe this is worth mentioning in the wiki https://wiki.sagemath.org/patchbot Even though I m

Re: [sage-devel] strange error message when raising an Error in cython()

try: : if c == 2: : raise IndexError() : except: : print 'error caught' : ''') error caught which solves my problem Am Mittwoch, 13. Februar 2019 11:21:32 UTC+1 schrieb Jeroen Demeyer: > > On 2019-02-13 11:02, jonathan.kliem via sage-devel

[sage-devel] strange error message when raising an Error in cython()

I'm getting a strange error when raising an error in cython(), example: sage: cython(''' : c = 2 : if c == 2: : raise IndexError() : ''') ERROR:root:An unexpected error occurred while tokenizing input The following traceback may be corrupted or invalid The error message is: ('E

[sage-devel] AlarmInterrupt causes Sage to crash hard

sage: alarm(1) sage: AlarmInterrupt escaped interact() sage: sage: