Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <402720651.1117723767466.JavaMail.jira@ajax.apache.org>
Date: Thu, 2 Jun 2005 16:49:27 +0200 (CEST)
From: "Kathey Marsden (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-320) Failed test:
 derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java
In-Reply-To: <1246566760.1117195982938.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ 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