#715: Parents probably not reclaimed due to too much caching
---------------------------------------------------------------------------+
Reporter: robertwb |
Owner: somebody
Type: defect |
Status: needs_review
Priority: major |
Milestone: sage-5.4
Component: coercion |
Resolution:
Keywords: weak cache coercion Cernay2012 |
Work issues:
Report Upstream: N/A |
Reviewers: Jean-Pierre Flori, Simon King, Nils Bruin
Authors: Simon King, Jean-Pierre Flori |
Merged in:
Dependencies: #9138, #11900, #11599, #13145, to be merged with #11521 |
Stopgaps:
---------------------------------------------------------------------------+
Comment (by SimonKing):
Replying to [comment:320 nbruin]:
> Perhaps if we equip every test with a line
> {{{
> >>> sys.stderr.write('testing test 6\n')
> }}}
> we may might be able to see the actual order in which the examples are
tested without preventing the doctest from happening.
<Deep sigh>
I tried, and printing to sys.stderr makes the segfault disappear. However,
it shows that the doctests ''are'' executed in alphabetical order: ...,
example_49, example_5, example_50, example_51, ..., example_67, example_7,
example_8, example_9.
Assuming that the same order is used when ''not'' printing to stderr, we
still find that the absence of a later doc test will prevent the segfault.
Namely, you located the segfault in example_27, but it won't occur when
deleting example_62, which comes alphabetically after example_27.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:321>
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.
