[
https://issues.apache.org/jira/browse/DERBY-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1760.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
10.2.2.1
Resolved by skipping final failing test with 10.2 (jdbcapi/_Suite.java) with
revision 500952 (http://svn.apache.org/viewvc?view=rev&revision=500952) and by
skipping jdbcapi/checkDataSource.java, jdbcapi/checkDataSource30.java,
lang/grantRevoke.java, and stress/stress.multi with trunk with revesion 500953
(http://svn.apache.org/viewvc?view=rev&revision=500953) by adding the tests to
the suites/DerbyNetClientRemote.exclude file.
> remote server testing with 10.2 snapshot showed 8 failures
> ----------------------------------------------------------
>
> Key: DERBY-1760
> URL: https://issues.apache.org/jira/browse/DERBY-1760
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.2.1, 10.3.0.0
>
>
> I ran derbynetclientmats between two IPV6 machines with the 10.2 snapshot and
> finally got to look at the results...There were 8 failures, 4 of those
> because of other tests leaving stuff behind.
> 2 tests complained about junit classes not being found (? one of those was
> checkDataSource!).
> 2 tests seemed to have trouble connecting - those might be the more
> interesting ones.
> Will do further analysis, & create test cleanup patches.
> The failing tests and some comments:
> suite derbynetclientmats with ibm142 & IPV6 machines using -DhostName= (i.e.
> remote server test) and build: 10.2.0.4 alpha - (419130)
> derbynetclientmats/derbynetclientmats.fail:jdbcapi/checkDataSource.java
> ?? fails because of an error accessing junit. Not sure why, junit is in
> client classpath...and it's not even a junit test. Stack trace not helpful.
> (points to client.am, which makes little/no sense).
> derbynetclientmats/derbynetmats/derbynetmats.fail:derbynet/testconnection.java
> ?? no connection
> derbynetclientmats/derbynetmats/derbynetmats.fail:derbynet/testij.java
> ?? no connection
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/metadata.java
> extra tables/views: JIRA1454, Y.
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/odbc_metadata.java
> ditto
> derbynetclientmats/derbynetmats/derbynetmats.fail:lang/syscat.sql
> ditto
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/ProcedureTest.junit
> junit not available??
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/checkDataSource30.java
> Table/View 'Y' already exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
