-
-
Notifications
You must be signed in to change notification settings - Fork 487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doctest killed due to abort in geometry/polyhedron/base.py #28866
Comments
comment:2
On the same machine, the following works, but takes long time
is it normal that it takes soo long? |
This comment has been minimized.
This comment has been minimized.
comment:5
Is there a particular reason for testing this? Otherwise I would just mark it as not tested. This points out that the hypercube is set up the wrong way. It takes much much longer to set it up from vertices than from inequalities:
With #28880 we could just provide both Vrepresentation and Hrepresentation whenever possible |
comment:6
Replying to @kliem:
This is a doctest for the
Yes, that would be the best fix for the hypercube. |
comment:7
Setting up the hypercube with Hrep will involve shuffling of vertices. I would like to wait with this until #28646 is through. |
comment:8
Ticket retargeted after milestone closed |
Dependencies: #29198 |
comment:12
Replying to @kliem: I tested with both #29198 and #29200. I now get a different error message (Memory error):
and the traceback that follows continues further than earlier:
|
comment:13
Is it possible that your run has very little memory available? I can get the tests to pass even with a memorylimit of 1400 MB. However, there are many obvious ways to reduce the memory usage, especially in this specific test:
|
comment:14
Does this solve the problem? New commits:
|
Branch: public/28866 |
Commit: |
Author: Jonathan Kliem |
comment:15
With the current branch, So it seems testing the file uses somewhere between 3400 and 3500 MB. On my machine, the default --memlimit is 3300 MB which explains the issue.
gives:
What is the default memlimit on your machine? |
comment:16
For comparison, I updated the description of the ticket with info about memlimit (3600 is ok, but 3500 fails on my machine on the latest develop version 9.1.beta9). |
This comment has been minimized.
This comment has been minimized.
comment:17
Can this be related to the optional packages I have installed?
On a another machine, I am able to run the test with
|
comment:18
As far as I know the default is the same everywhere. 3300MB. As already mentioned the following passes (also on 9.1.beta9):
So maybe that is not an issue of |
comment:19
Yes, but I get that issue only for that file. |
comment:20
The other thing you could try is doing a garbage collection somewhere along the way in the doctests. I don't know, if that would make a difference. One could hide this somewhere in some |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
comment:48
I'm sorry, can you teach me how I can figure this out?
Ok, I will test that. |
comment:49
Replying to @seblabbe:
There's probably nothing unusual here, but:
should show the relevant stuff on linux. On mac or windows I would have to resort to google. |
comment:50
This is the output on the machine having trouble:
|
comment:51
(Note that when I pushed the branch on the ticket, it automatically set the ticket to needs_review again (it seems to be a new feature), so I let you review my commit) |
Changed reviewer from Michael Orlitzky to Sébastien Labbé, Michael Orlitzky |
comment:53
Replying to @seblabbe:
Nothing unusual. Another thing I thought of: if recompiling everything with
should show which which system packages are being used. |
comment:54
On Python 2:
|
Changed reviewer from Sébastien Labbé, Michael Orlitzky to Sébastien Labbé, Michael Orlitzky, Matthias Koeppe |
comment:57
Looks good to me |
Changed branch from public/28866-reb to |
Changed commit from |
comment:59
I introduced a bug in this ticket: The double description for intervals is completely wrong. Please review #29904. |
On a clean develop branch running
SageMath version 9.1.beta9, Release Date: 2020-03-29
, I get:while
or
gives
CC: @mkoeppe @jplab @orlitzky
Component: geometry
Author: Jonathan Kliem
Branch:
c701c31
Reviewer: Sébastien Labbé, Michael Orlitzky, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/28866
The text was updated successfully, but these errors were encountered: