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 "Bernt M. Johnsen (JIRA)" <de...@db.apache.org> on 2005/05/27 14:13:02 UTC

[jira] Created: (DERBY-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
---------------------------------------------------------------------------------------

         Key: DERBY-320
         URL: http://issues.apache.org/jira/browse/DERBY-320
     Project: Derby
        Type: Bug
  Components: Test  
    Reporter: Bernt M. Johnsen


When running derbyall, DerbyNetClient/lang/updatableResultSet fails
the following way:
                                                                                                                                                                        
*** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:12:55 ***
Initialize for framework: DerbyNetClient
java -ms16777216 -mx33554432 -Dderby.system.home=/export/home/tmp/Derby/test/Der byNetClient/updatableResultSet -Djava.security.manager -Djava.security.policy=/e
+xport/home/tmp/Derby/test/nwsvr.policy -Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane -Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
+.apache.derby.drda.NetworkServerControl start
Attempt to shutdown framework: DerbyNetClient
310 del
< Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.
310a310
> Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.
317 del
<       SQL_CURLH000C55
317a317
>       SQL_CURLH000C54
Test Failed.
*** End:   updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:13:22 ***
                                                                                                                                                                        
(Same error with 1.5 and 1.3)
                                                                                                                                                                        
I'm running with Linux 2.6.11. What I find strange, is that when I
inspect the test failures in
http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-178249.html
I see that the same test fails in the same way on all platforms,
with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08


>>>>>>>>>>>> Myrna van Lunteren wrote (2005-05-26 14:36:59):
> Without looking at the test or any -recent- changes, I'm giving this as my 2 
> cents:
>  If that cursorname is generated, and if a generated cursorname does not 
> need to be identical in the same scenario on all system/jvm combinations, 
> then the name should get out of the output.
> i.e. either in the test it should not print the cursor names, or, if that is 
> not feasible, it should get masked by adding appropriate lines to 
> updatableResultSet_sed.properties.
>  Myrna


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


Re: [jira] Commented: (DERBY-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

Posted by Kathey Marsden <km...@sbcglobal.net>.
Kathey Marsden (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/DERBY-320?page=comments#action_66866 ]
>     
>Kathey Marsden commented on DERBY-320:
>--------------------------------------
>
>Committed this change.
>Sending        java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\updatableResultSet.out
>Sending        java\testing\org\apache\derbyTesting\functionTests\tests\lang\copyfiles.ant
>Adding         java\testing\org\apache\derbyTesting\functionTests\tests\lang\updatableResultSet_sed.properties
>Transmitting file data ...
>Committed revision 179592.
>
>  
>
I committed this change but just after hitting enter it occurred to me
that I didn't fully understand why the cursor names were different. It
seems like that would be a deterministic thing.  Mamta, could you please
double check that this was the right change to make?

Thanks

Kathey




[jira] Commented: (DERBY-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-320?page=comments#action_66866 ]
     
Kathey Marsden commented on DERBY-320:
--------------------------------------

Committed this change.
Sending        java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\updatableResultSet.out
Sending        java\testing\org\apache\derbyTesting\functionTests\tests\lang\copyfiles.ant
Adding         java\testing\org\apache\derbyTesting\functionTests\tests\lang\updatableResultSet_sed.properties
Transmitting file data ...
Committed revision 179592.

> Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-320
>          URL: http://issues.apache.org/jira/browse/DERBY-320
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Reporter: Bernt M. Johnsen
>     Assignee: David Van Couvering
>  Attachments: DERBY-320.diff
>
> When running derbyall, DerbyNetClient/lang/updatableResultSet fails
> the following way:
>                                                                                                                                                                         
> *** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:12:55 ***
> Initialize for framework: DerbyNetClient
> java -ms16777216 -mx33554432 -Dderby.system.home=/export/home/tmp/Derby/test/Der byNetClient/updatableResultSet -Djava.security.manager -Djava.security.policy=/e
> +xport/home/tmp/Derby/test/nwsvr.policy -Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane -Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
> +.apache.derby.drda.NetworkServerControl start
> Attempt to shutdown framework: DerbyNetClient
> 310 del
> < Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.
> 310a310
> > Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.
> 317 del
> <       SQL_CURLH000C55
> 317a317
> >       SQL_CURLH000C54
> Test Failed.
> *** End:   updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:13:22 ***
>                                                                                                                                                                         
> (Same error with 1.5 and 1.3)
>                                                                                                                                                                         
> I'm running with Linux 2.6.11. What I find strange, is that when I
> inspect the test failures in
> http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-178249.html
> I see that the same test fails in the same way on all platforms,
> with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08
> >>>>>>>>>>>> Myrna van Lunteren wrote (2005-05-26 14:36:59):
> > Without looking at the test or any -recent- changes, I'm giving this as my 2 
> > cents:
> >  If that cursorname is generated, and if a generated cursorname does not 
> > need to be identical in the same scenario on all system/jvm combinations, 
> > then the name should get out of the output.
> > i.e. either in the test it should not print the cursor names, or, if that is 
> > not feasible, it should get masked by adding appropriate lines to 
> > updatableResultSet_sed.properties.
> >  Myrna

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


Re: [jira] Updated: (DERBY-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

Posted by Kathey Marsden <km...@sbcglobal.net>.
David Van Couvering (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/DERBY-320?page=all ]
>
>David Van Couvering updated DERBY-320:
>--------------------------------------
>
>    Attachment: DERBY-320.diff
>
>Attaching a patch that fixes this bug. 
>

Thanks David!

I'll check this in.



[jira] Updated: (DERBY-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

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

David Van Couvering updated DERBY-320:
--------------------------------------

    Attachment: DERBY-320.diff

Attaching a patch that fixes this bug.  I created a sed file to filter out
the cursor name.  I did this only for DerbyNetClient as this has not been
an issue for embedded.

I ran derbyall, all tests passed.

output of svn status:

M      java/testing/org/apache/derbyTesting/functionTests/tests/lang/copyfiles.ant
A      java/testing/org/apache/derbyTesting/functionTests/tests/lang/updatableResultSet_sed.properties
M      java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/updatableResultSet.out


> Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-320
>          URL: http://issues.apache.org/jira/browse/DERBY-320
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Reporter: Bernt M. Johnsen
>     Assignee: David Van Couvering
>  Attachments: DERBY-320.diff
>
> When running derbyall, DerbyNetClient/lang/updatableResultSet fails
> the following way:
>                                                                                                                                                                         
> *** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:12:55 ***
> Initialize for framework: DerbyNetClient
> java -ms16777216 -mx33554432 -Dderby.system.home=/export/home/tmp/Derby/test/Der byNetClient/updatableResultSet -Djava.security.manager -Djava.security.policy=/e
> +xport/home/tmp/Derby/test/nwsvr.policy -Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane -Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
> +.apache.derby.drda.NetworkServerControl start
> Attempt to shutdown framework: DerbyNetClient
> 310 del
> < Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.
> 310a310
> > Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.
> 317 del
> <       SQL_CURLH000C55
> 317a317
> >       SQL_CURLH000C54
> Test Failed.
> *** End:   updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:13:22 ***
>                                                                                                                                                                         
> (Same error with 1.5 and 1.3)
>                                                                                                                                                                         
> I'm running with Linux 2.6.11. What I find strange, is that when I
> inspect the test failures in
> http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-178249.html
> I see that the same test fails in the same way on all platforms,
> with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08
> >>>>>>>>>>>> Myrna van Lunteren wrote (2005-05-26 14:36:59):
> > Without looking at the test or any -recent- changes, I'm giving this as my 2 
> > cents:
> >  If that cursorname is generated, and if a generated cursorname does not 
> > need to be identical in the same scenario on all system/jvm combinations, 
> > then the name should get out of the output.
> > i.e. either in the test it should not print the cursor names, or, if that is 
> > not feasible, it should get masked by adding appropriate lines to 
> > updatableResultSet_sed.properties.
> >  Myrna

-- 
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-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-320?page=all ]
     
Bernt M. Johnsen closed DERBY-320:
----------------------------------


Verified on revision 180256M:

Java Version:    1.5.0_03
Java Vendor:     Sun Microsystems Inc.
OS name:         Linux
OS architecture: i386
OS version:      2.4.20-31.9


> Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-320
>          URL: http://issues.apache.org/jira/browse/DERBY-320
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Reporter: Bernt M. Johnsen
>     Assignee: David Van Couvering
>      Fix For: 10.1.0.0
>  Attachments: DERBY-320.diff
>
> When running derbyall, DerbyNetClient/lang/updatableResultSet fails
> the following way:
>                                                                                                                                                                         
> *** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:12:55 ***
> Initialize for framework: DerbyNetClient
> java -ms16777216 -mx33554432 -Dderby.system.home=/export/home/tmp/Derby/test/Der byNetClient/updatableResultSet -Djava.security.manager -Djava.security.policy=/e
> +xport/home/tmp/Derby/test/nwsvr.policy -Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane -Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
> +.apache.derby.drda.NetworkServerControl start
> Attempt to shutdown framework: DerbyNetClient
> 310 del
> < Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.
> 310a310
> > Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.
> 317 del
> <       SQL_CURLH000C55
> 317a317
> >       SQL_CURLH000C54
> Test Failed.
> *** End:   updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:13:22 ***
>                                                                                                                                                                         
> (Same error with 1.5 and 1.3)
>                                                                                                                                                                         
> I'm running with Linux 2.6.11. What I find strange, is that when I
> inspect the test failures in
> http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-178249.html
> I see that the same test fails in the same way on all platforms,
> with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08
> >>>>>>>>>>>> Myrna van Lunteren wrote (2005-05-26 14:36:59):
> > Without looking at the test or any -recent- changes, I'm giving this as my 2 
> > cents:
> >  If that cursorname is generated, and if a generated cursorname does not 
> > need to be identical in the same scenario on all system/jvm combinations, 
> > then the name should get out of the output.
> > i.e. either in the test it should not print the cursor names, or, if that is 
> > not feasible, it should get masked by adding appropriate lines to 
> > updatableResultSet_sed.properties.
> >  Myrna

-- 
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-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

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

David Van Couvering reassigned DERBY-320:
-----------------------------------------

    Assign To: David Van Couvering

> Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-320
>          URL: http://issues.apache.org/jira/browse/DERBY-320
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Reporter: Bernt M. Johnsen
>     Assignee: David Van Couvering

>
> When running derbyall, DerbyNetClient/lang/updatableResultSet fails
> the following way:
>                                                                                                                                                                         
> *** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:12:55 ***
> Initialize for framework: DerbyNetClient
> java -ms16777216 -mx33554432 -Dderby.system.home=/export/home/tmp/Derby/test/Der byNetClient/updatableResultSet -Djava.security.manager -Djava.security.policy=/e
> +xport/home/tmp/Derby/test/nwsvr.policy -Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane -Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
> +.apache.derby.drda.NetworkServerControl start
> Attempt to shutdown framework: DerbyNetClient
> 310 del
> < Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.
> 310a310
> > Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.
> 317 del
> <       SQL_CURLH000C55
> 317a317
> >       SQL_CURLH000C54
> Test Failed.
> *** End:   updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:13:22 ***
>                                                                                                                                                                         
> (Same error with 1.5 and 1.3)
>                                                                                                                                                                         
> I'm running with Linux 2.6.11. What I find strange, is that when I
> inspect the test failures in
> http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-178249.html
> I see that the same test fails in the same way on all platforms,
> with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08
> >>>>>>>>>>>> Myrna van Lunteren wrote (2005-05-26 14:36:59):
> > Without looking at the test or any -recent- changes, I'm giving this as my 2 
> > cents:
> >  If that cursorname is generated, and if a generated cursorname does not 
> > need to be identical in the same scenario on all system/jvm combinations, 
> > then the name should get out of the output.
> > i.e. either in the test it should not print the cursor names, or, if that is 
> > not feasible, it should get masked by adding appropriate lines to 
> > updatableResultSet_sed.properties.
> >  Myrna

-- 
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-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-320?page=all ]
     
David Van Couvering resolved DERBY-320:
---------------------------------------

     Resolution: Fixed
    Fix Version: 10.1.0.0

Bernt, can you verify and close?

> Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-320
>          URL: http://issues.apache.org/jira/browse/DERBY-320
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Reporter: Bernt M. Johnsen
>     Assignee: David Van Couvering
>      Fix For: 10.1.0.0
>  Attachments: DERBY-320.diff
>
> When running derbyall, DerbyNetClient/lang/updatableResultSet fails
> the following way:
>                                                                                                                                                                         
> *** Start: updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:12:55 ***
> Initialize for framework: DerbyNetClient
> java -ms16777216 -mx33554432 -Dderby.system.home=/export/home/tmp/Derby/test/Der byNetClient/updatableResultSet -Djava.security.manager -Djava.security.policy=/e
> +xport/home/tmp/Derby/test/nwsvr.policy -Dcsinfo.codebase=/export/home/tmp/Derby/ trunk/jars/sane -Dcsinfo.serverhost=localhost -Dcsinfo.trustedhost=localhost org
> +.apache.derby.drda.NetworkServerControl start
> Attempt to shutdown framework: DerbyNetClient
> 310 del
> < Got expected exception Cursor 'SQL_CURLH000C52' is not on a row.
> 310a310
> > Got expected exception Cursor 'SQL_CURLH000C51' is not on a row.
> 317 del
> <       SQL_CURLH000C55
> 317a317
> >       SQL_CURLH000C54
> Test Failed.
> *** End:   updatableResultSet jdk1.4.2_02 DerbyNetClient 2005-05-26 23:13:22 ***
>                                                                                                                                                                         
> (Same error with 1.5 and 1.3)
>                                                                                                                                                                         
> I'm running with Linux 2.6.11. What I find strange, is that when I
> inspect the test failures in
> http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-178249.html
> I see that the same test fails in the same way on all platforms,
> with the exception of the test run on a Linux 2.4.19 and jdk1.4.2_08
> >>>>>>>>>>>> Myrna van Lunteren wrote (2005-05-26 14:36:59):
> > Without looking at the test or any -recent- changes, I'm giving this as my 2 
> > cents:
> >  If that cursorname is generated, and if a generated cursorname does not 
> > need to be identical in the same scenario on all system/jvm combinations, 
> > then the name should get out of the output.
> > i.e. either in the test it should not print the cursor names, or, if that is 
> > not feasible, it should get masked by adding appropriate lines to 
> > updatableResultSet_sed.properties.
> >  Myrna

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