Follow-up to r1235264: add two new tests to aid in detecting memory leaks. They essentially test the same thing in two different ways; if one fails, the other *should* fail.  (Of course, if one fails and the other does not -- that's just as valuable, diagnostically, and points to an issue with the 'automatic pool memory management' logic.)
Follow-up to r1235264: add two new tests to aid in detecting memory leaks.
They essentially test the same thing in two different ways; if one fails,
the other *should* fail.  (Of course, if one fails and the other does not --
that's just as valuable, diagnostically, and points to an issue with the
'automatic pool memory management' logic.)

Patch by: Trent Nelson <trent@snakebite.org>
Tested on: FreeBSD, OS X, Windows.
(split from r1235264 by me)

* subversion/bindings/swig/python/tests/mergeinfo.py:
  (get_svn_merge_range_t_objects): New helper method that returns a list of
   any 'svn_merge_range_t' objects being tracked by the garbage collector.
  (SubversionMergeinfoTestCase): 
    (test_mergeinfo_leakage__incorrect_range_t_refcounts): New test.  Verify
     svn_merge_range_t objects returned from svn_mergeinfo_parse() have the
     correct refcounts set.
    (test_mergeinfo_leakage__lingering_range_t_objects_after_del): New test.
     Verify that there are no lingering svn_merge_range_t objects after we
     explicitly delete the results returned from svn_mergeinfo_parse().

jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion