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 "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2006/08/25 01:39:15 UTC
[jira] Created: (DERBY-1760) remote server testing with 10.2
snapshot showed 8 failures
remote server testing with 10.2 snapshot showed 8 failures
----------------------------------------------------------
Key: DERBY-1760
URL: http://issues.apache.org/jira/browse/DERBY-1760
Project: Derby
Issue Type: Test
Components: Test
Affects Versions: 10.2.1.0
Reporter: Myrna van Lunteren
Assigned To: Myrna van Lunteren
Priority: Minor
Fix For: 10.2.1.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.
-
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-1760) remote server testing with 10.2
snapshot showed 8 failures
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1760?page=all ]
Myrna van Lunteren updated DERBY-1760:
--------------------------------------
Fix Version/s: (was: 10.2.2.0)
Changing this to unknown. It's not something that should stop release of any 10.2 version.
What gets fixed though needs to happen at least on the 10.2 branch. 10.3 uses (more) junit testing and DERBY-1973 is open for implementing remote server testing with that.
> remote server testing with 10.2 snapshot showed 8 failures
> ----------------------------------------------------------
>
> Key: DERBY-1760
> URL: http://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
>
> 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.
-
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-1760) remote server testing with 10.2
snapshot showed 8 failures
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468148 ]
Myrna van Lunteren commented on DERBY-1760:
-------------------------------------------
I did another run to see what the current state of this is, so I can close this issue.
The 10.2 test run resulted in 1 failure:
------------------------------------------
E
Time: 0.172
There was 1 error:
1) jdbcapijava.security.AccessControlException: access denied (java.net.SocketPermission hope.usca.ibm.com resolve)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.SecurityManager.checkConnect(SecurityManager.java:1023)
at java.net.InetAddress.getAllByName0(InetAddress.java:1000)
at java.net.InetAddress.getAllByName0(InetAddress.java:981)
at java.net.InetAddress.getAllByName(InetAddress.java:975)
at java.net.InetAddress.getByName(InetAddress.java:889)
at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:80)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.extensions.TestSetup.run(TestSetup.java:23)
FAILURES!!!
Tests run: 0, Failures: 0, Errors: 1
-----------------------------------
I'm not sure what changed since last time I ran this, but rather then spend time trying to backtrack, I'm going to exclude this test also from the remoteserver run.
With main, I got the following failures:
---------------------------------
derbynetclientmats/derbynetclientmats.fail:jdbcapi/checkDataSource.java
derbynetclientmats/derbynetclientmats.fail:lang/grantRevoke.java
derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/metadata.java
derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/odbc_metadata.java
derbynetclientmats/derbynetmats/derbynetmats.fail:lang/procedure.java
derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/resultset.java
derbynetclientmats/derbynetmats/derbynetmats.fail:stress/stress.multi
derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/checkDataSource30.java
--------------------------------
So, mostly the same as initially with 10.2.
I will add these to the DerbyNetClient.exclude file also.
> 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
>
> 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.
[jira] Closed: (DERBY-1760) remote server testing with 10.2
snapshot showed 8 failures
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-1760) remote server testing with 10.2
snapshot showed 8 failures
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1760?page=comments#action_12451019 ]
Myrna van Lunteren commented on DERBY-1760:
-------------------------------------------
Moved this closer to resolving by committing
http://svn.apache.org/viewvc?view=rev&revision=476529
> remote server testing with 10.2 snapshot showed 8 failures
> ----------------------------------------------------------
>
> Key: DERBY-1760
> URL: http://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.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.
-
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-1760) remote server testing with 10.2
snapshot showed 8 failures
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1760?page=all ]
Rick Hillegas updated DERBY-1760:
---------------------------------
Fix Version/s: 10.2.2.0
(was: 10.2.1.0)
Moving to 10.2.2.0.
> remote server testing with 10.2 snapshot showed 8 failures
> ----------------------------------------------------------
>
> Key: DERBY-1760
> URL: http://issues.apache.org/jira/browse/DERBY-1760
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.2.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.
-
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