Hi Kathey,
I ran this test with different profiles, that is on machines having different Operating Systems and also
when the load on the systems were high. I did not notice this test failing even once.
The message in the master says Unexpected Exception, actaully a SQLExcpetion is being caught and the message
from there displayed. I can change the message if you want, but I don't see any other problem.
thanks Shreyas
Kathey Marsden wrote:
jdbcapi/testRelative seems to be failing intermittently.
6a7 > SQL Exception: Invalid cursor state - no current row. 9 del < SQL Exception: Invalid cursor state - no current row. Test Failed.
It might be a timing issue related to doing a sqle.printStackTrace() in the case of an expected exception. The master shows that we have an unexpected exception which doesn't make sense in the master. Generally only expected exceptions would be checked into the master and would not print a stack trace. Unexpected exceptions should cause the test to fail and should print a stack trace.
Shreyas could you take a look at this?
Thanks
Kathey
