You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Oyvind Bakksjo (JIRA)" <de...@db.apache.org> on 2005/11/14 16:51:28 UTC

[jira] Created: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Re-enable test which was disabled in DERBY-506 commit
-----------------------------------------------------

         Key: DERBY-705
         URL: http://issues.apache.org/jira/browse/DERBY-705
     Project: Derby
        Type: Test
  Components: Test  
    Reporter: Oyvind Bakksjo
    Priority: Trivial


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


[jira] Resolved: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-705?page=all ]

Knut Anders Hatlen resolved DERBY-705.
--------------------------------------

    Fix Version/s: 10.2.1.0
       Resolution: Fixed

Thanks, Narayanan!

Committed into trunk with revision 437168.
Committed into 10.2 with revision 437169.

> 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
>             Fix For: 10.2.1.0
>
>         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

        

[jira] Assigned: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-705?page=all ]

V.Narayanan reassigned DERBY-705:
---------------------------------

    Assignee: V.Narayanan

> 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
>
> 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

        

[jira] Updated: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-705?page=all ]

V.Narayanan updated DERBY-705:
------------------------------

    Attachment: DERBY-705.diff
                DERBY-705.stat

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.

thanx
Narayanan

> 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

        

[jira] Commented: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Posted by "V.Narayanan (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-705?page=comments#action_12430916 ] 
            
V.Narayanan commented on DERBY-705:
-----------------------------------

Thanx a ton for taking a look at the patch and giving it a commit.

> 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
>             Fix For: 10.2.1.0
>
>         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

        

[jira] Closed: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-705.
------------------------------------


> Re-enable test which was disabled in DERBY-506 commit
> -----------------------------------------------------
>
>                 Key: DERBY-705
>                 URL: https://issues.apache.org/jira/browse/DERBY-705
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Oyvind Bakksjo
>         Assigned To: V.Narayanan
>            Priority: Trivial
>             Fix For: 10.2.1.6
>
>         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.
-
You can reply to this email to add a comment to the issue online.