#13880: Respect ulimit -v for GAP memory pool size
--------------------------------+-------------------------------------------
Reporter: vbraun | Owner: jason
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-5.6
Component: misc | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by dimpase):
I am testing this on a system where mem.available_swap() comes up
negative:
{{{
sage: t = mem._parse_proc_meminfo(); t
{'available_ram': 1435963392, 'total_swap': 10909376512, 'available_swap':
8558673920, 'Committed_AS': 16000847872, 'total_ram': 7929249792}
sage: mem.available_swap()
-5091471360
}}}
which is not surprising, as mem.available_swap() computes {{{
t['total_swap']-t['Committed_AS']}}}, rather than returning
{{{t['available_swap']}}}.
What is going on? A bug or a feature?
That's how far I get digging up the cause of
{{{
sage -t -long "devel/sage-main/sage/misc/memory_info.py"
**********************************************************************
File "/usr/local/src/sage/sage-5.5/devel/sage-
main/sage/misc/memory_info.py", line 122:
sage: mem.virtual_memory_limit() > 0
Expected:
True
Got:
False
**********************************************************************
1 items had failures:
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13880#comment:19>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
