Hi Phil,
The change looks fine.
Jennifer
On 10/27/2014 02:49 PM, Phil Race wrote:
I can add othervm but each VM invocation slows down the
overall testing time and I'd like to think this only will be run on
versions that do not have the bug.
I added the custom time out code so that I was not
Hi, Jim, Phil.
I just look at this code and have a related question. Why we cannot clip
source coordinates(using invers transform)? This:
- solve this issue
- speedup all our general loops, which are based on intermediate
buffers(including renderImageXform())
- we can return earlier if a
The fix looks fine. Isn't there a timeout you can set on the unit test
rather than rolling your own inside the test? Also, even if you
interrupt the test, if the failure mode is an infinite loop in native
code then the VM you are running in is probably not going to be happy.
That only
I can add othervm but each VM invocation slows down the
overall testing time and I'd like to think this only will be run on
versions that do not have the bug.
I added the custom time out code so that I was not reliant on the
harness to test.
Certainly I can delete all of that and just go to
That looks good. You bring up good points as well. The main thing I
was worried about is hanging an automated regression test run if there
is ever a regression...
...jim
On 10/27/14 2:49 PM, Phil Race wrote:
I can add othervm but each VM invocation slows down the
overall