#9863: Error in sage/graphs/genus.pyx on ia64-Linux-suse
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.6
Component: doctest | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by mderickx):
I find the test code which causes al the discussion in this ticket broken.
The code tries to test if the deallocation of
simple_connected_genus_backtracker works so to prevent memory leaks. But
when I test it in sage (on os x 10.6 since I don't have acces to a suse
installation) I get the following result with measuring how many memory
the backtracker actually takes:
{{{
sage: import sage.graphs.genus
sage: G = graphs.!CompleteGraph(100)
sage: G = Graph(G, implementation='c_graph', sparse=False)
sage: t = get_memory_usage()
sage: gb =
sage.graphs.genus.simple_connected_genus_backtracker(G._backend._cg)
sage: get_memory_usage(t)
0.0
sage: gb = None #indirect doctest
sage: get_memory_usage(t)
0.0
}}}
So the backtracker seems to take an unmeasurable amount of memory in the
first place, deallocation working properly is therefore not tested at all.
(at least not os os x 10.6, I would love to see this test replicated on
the machine on which the paralel doctesting gives errors).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9863#comment:4>
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.
