[Orbit-python-list] Re: Stress test suite added.

[Jason T. <ta...@li...>]

> perform the requests and how much was leaked. The client-side leak reports
> are probably bogus at this point (since it reports leaking even though we
> all know orbit-python doesn't leak *grin*) but I'll work on it through the
> weekend if my visiting parents don't occupy me too much.

Well I went on that leak squashing binge last week and O-P doesn't leak
in most common cases, but for error conditions there might very well be
leaks.  So I'll look at that for sure, but not too closely until after
0.3.0 is released. 

> Jason, orbit-python as of now doesn't run the basic tests anymore! ORBPOA
> tests all fail when trying to run resolve_initial_references("RootPOA")

I see that!  Did you make any additional changes to the tests?  Because
two of the failures were attributed to ORBit bugs, and I can't see them
passing before.

The first is passing a bad value ("XXX") to resolve_initial_references.
It correctly fails, but then any subsequent call segfaults inside ORBit.

   http://bugzilla.gnome.org/show_bug.cgi?id=55726

The second causes string_to_object to incorrectly fail given a valid IOR
if it was previously invoked with an invalid IOR ("foo" say).

   http://bugzilla.gnome.org/show_bug.cgi?id=55729

I don't know how quickly these will get addressed.  The other bug I
reported didn't get acknowledged at all.

A few of the other tests in the test suite were rendered invalid by my
recent changes of moving implicit activation into servant_to_reference,
so you can call servant_to_reference in a non-active servant and it will
activate it if the POA supports implicit activation.

Anyway, I fixed the test suite up so it passes again. 

Jason.