On Sunday 10 August 2008 4:06:06 pm Benson Margulies wrote:
I see what the problem is here. I'm making an assumption about two things
that might not happen in the order I expect. I'll try to think of some
better way of handling it.
I think you nailed it. I ran the test 20 times and it didn't
I see what the problem is here. I'm making an assumption about two things
that might not happen in the order I expect. I'll try to think of some
better way of handling it.
On Tue, Aug 5, 2008 at 8:37 PM, Daniel Kulp [EMAIL PROTECTED] wrote:
Benson,
I'm back on Linux again and I'm now seeing
I got swamped. I'll get there eventually.
On Wed, Aug 6, 2008 at 12:45 PM, Benson Margulies [EMAIL PROTECTED]wrote:
The recent change of possible relevance is to make asynchronous operations
against the simulated browser be really asynchronous.
This particular test is the one I labored over
On Thursday 07 August 2008 7:34:49 am Benson Margulies wrote:
I got swamped. I'll get there eventually.
No problem. I through a System.gc() in there and the problem became much
less apparent so it isn't bothing me as much. :-) Maybe 10% from top
level. It's probably not really related
The recent change of possible relevance is to make asynchronous operations
against the simulated browser be really asynchronous.
This particular test is the one I labored over for the woman who ran into
the multiple request issue, so sadly it's unlikely to be suffering from some
trivial problem.
Benson,
I'm back on Linux again and I'm now seeing a somewhat random test failure in
the javascript module. (50% failure when run top level, less so from within
the module) I'm not sure what to make of it or what could be causing it.
It also doesn't seem to occur in eclipse so I'm not
