db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit
Date Wed, 16 Aug 2006 11:55:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-705?page=all ]

V.Narayanan updated DERBY-705:

    Attachment: DERBY-705.diff

Followed the instructions in the comments of SetQueryTimeoutTest.java to enable the test to
run when multiple statements are executed in the same connections. I then did the following

1) Ran the test in Embedded
     result:- passed
2) Ran the test with framework as DerbyNetClient
     result - passed
3) Ran the test with framework as DerbyNet. 
     result - It was skipped as expected since there is  an entry for 
                   jdbcapi/SetQueryTimeout.java in DerbyNet.exclude.


> Re-enable test which was disabled in DERBY-506 commit
> -----------------------------------------------------
>                 Key: DERBY-705
>                 URL: http://issues.apache.org/jira/browse/DERBY-705
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Oyvind Bakksjo
>         Assigned To: V.Narayanan
>            Priority: Trivial
>         Attachments: DERBY-705.diff, DERBY-705.stat
> Testing of concurrent executions on same connection was disabled in DERBY-506 commit
because of DERBY-694 bug. Re-enable when DERBY-694 is fixed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message