[jira] Commented: (DERBY-4231) testReplication_Local_StateTest_part1: Unexpected SQL state. expected:XRE[20] but was:XRE[07]
[ https://issues.apache.org/jira/browse/DERBY-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709773#action_12709773 ] Henri van de Scheur commented on DERBY-4231: I think this is DERBY-3719: Looks like the same signature: http://dbtg.thresher.com/derby/FailSigs/3719.1.html. See 3719 in http://dbtg.thresher.com/derby/test/stats_newest.html for other occurrences. testReplication_Local_StateTest_part1: Unexpected SQL state. expected:XRE[20] but was:XRE[07] - Key: DERBY-4231 URL: https://issues.apache.org/jira/browse/DERBY-4231 Project: Derby Issue Type: Bug Components: Regression Test Failure, Replication Reporter: Dag H. Wanvik Priority: Minor Attachments: derby.log.master, derby.log.slave This is another instability in the replication tests I see occasionally. I was able to reproduce it just now in of of 70 runs. 1) testReplication_Local_StateTest_part1(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1)junit.framework.ComparisonFailure: Unexpected SQL state. expected:XRE[20] but was:XRE[07] at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:762) at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:811) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1382) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver(ReplicationRun.java:1303) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1.testReplication_Local_StateTest_part1(ReplicationRun_Local_StateTest_part1.java:168) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) Caused by: java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the database is not in replication master mode. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:96) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:358) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149) at java.sql.DriverManager.getConnection(DriverManager.java:582) at java.sql.DriverManager.getConnection(DriverManager.java:207) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1369) ... 24 more Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the database is not in replication master mode. at org.apache.derby.client.am.Connection.completeSqlca(Connection.java:2082) at org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(NetConnectionReply.java:540) at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:433) at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:297) at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:121) at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:835) at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:759) at org.apache.derby.client.net.NetConnection.flowUSRIDONLconnect(NetConnection.java:592) at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:399) at org.apache.derby.client.net.NetConnection.init(NetConnection.java:219) at org.apache.derby.client.net.NetConnection40.init(NetConnection40.java:77) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140) ... 27 more I attach derby.log for master and slave. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4231) testReplication_Local_StateTest_part1: Unexpected SQL state. expected:XRE[20] but was:XRE[07]
[ https://issues.apache.org/jira/browse/DERBY-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur updated DERBY-4231: --- Comment: was deleted (was: I think this is DERBY-3719: Looks like the same signature: http://dbtg.thresher.com/derby/FailSigs/3719.1.html. See 3719 in http://dbtg.thresher.com/derby/test/stats_newest.html for other occurrences. ) testReplication_Local_StateTest_part1: Unexpected SQL state. expected:XRE[20] but was:XRE[07] - Key: DERBY-4231 URL: https://issues.apache.org/jira/browse/DERBY-4231 Project: Derby Issue Type: Bug Components: Regression Test Failure, Replication Reporter: Dag H. Wanvik Priority: Minor Attachments: derby.log.master, derby.log.slave This is another instability in the replication tests I see occasionally. I was able to reproduce it just now in of of 70 runs. 1) testReplication_Local_StateTest_part1(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1)junit.framework.ComparisonFailure: Unexpected SQL state. expected:XRE[20] but was:XRE[07] at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:762) at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:811) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1382) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver(ReplicationRun.java:1303) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1.testReplication_Local_StateTest_part1(ReplicationRun_Local_StateTest_part1.java:168) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) Caused by: java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the database is not in replication master mode. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:96) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:358) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149) at java.sql.DriverManager.getConnection(DriverManager.java:582) at java.sql.DriverManager.getConnection(DriverManager.java:207) at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1369) ... 24 more Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the database is not in replication master mode. at org.apache.derby.client.am.Connection.completeSqlca(Connection.java:2082) at org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(NetConnectionReply.java:540) at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:433) at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:297) at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:121) at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:835) at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:759) at org.apache.derby.client.net.NetConnection.flowUSRIDONLconnect(NetConnection.java:592) at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:399) at org.apache.derby.client.net.NetConnection.init(NetConnection.java:219) at org.apache.derby.client.net.NetConnection40.init(NetConnection40.java:77) at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269) at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140) ... 27 more I attach derby.log for master and slave. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Code Coverage Results for 10.4.1.3
Hi again! I do not understand these differences. I have instrumented the same jars, but not all. I did not include derbyTesting.jar and the derbyLocale*.jars. So I instrumented the 5 following jars: derby.jar, derbyclient.jar, derbynet.jar, derbyrun.jar and derbytools.jar. I hope to find an explanation when I can compare your reports with mine. Henri Manjula Kutty wrote: I took the 10.4.1.3 http://10.4.1.3 Release candidate jars. I used the sun jdks. Also is there a chance that I was giving all permission to all the codebases in the derby_tests policy file? -Manjula On 5/7/08, *Henri van de Scheur* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Manjula! I was able to fix the problem with linking the source-code, so now the site I mentioned before shows correct and complete results. To summarize and compare with your results: OVERALL COVERAGE SUMMARY -- all classes: 90% (1264/1397) Method : 75% (16948/22513) Block : 73% (479495/660441) Line : 71% (100760/141054) OVERALL STATS SUMMARY total packages: 89 total executable files: 1280 total classes: 1397 total methods: 22513 total executable lines: 141054 So we see a couple of (general) differences: 1. In general you report higher numbers for the totals 2. In general I find higher numbers for coverage Can this be explained by just the differences in our jvm's (as different vendors) or should we investigate more? For my numbers I did a little workaround regarding the source-code: I used the source-code from the 10.4-branch and not the official 10.4.1.3 http://10.4.1.3/ Thanks ! Henri Manjula Kutty wrote: Hi Henri I ran suites.all. I used my derby_tests policy (Actually the one which gives all permission). I ran it with jdk142, 15 and 16. I will be linking the full report to the wiki. Thanks Manjula On 5/6/08, *Henri van de Scheur* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Manjula Kutty wrote: OVERALL COVERAGE SUMMARY -- all classes: 87% (1226/1404) Method : 74% (16629/22556) Block : 69% (486715/704201) Line : 69% (101022.4/146764) OVERALL STATS SUMMARY total packages: 90 total executable files: 1286 total classes: 1404 total methods: 22556 total executable lines: 146764 -- Thanks, Manjula. Hi Manjula! What testsuite did you use and which jvm-versions? I used Emma to run with suitesAll on jvm1.4, jvm1.5 and jvm1.6 (both 32- and 64-mode). Results can be found here: http://dbtg.thresher.com/derby/test/10.4.1.3_RC/Emma.html Unfortunately I have had some problems linking the source-code to these reports, but I plan to do that within the next 24 hours (if svn allows me). Thanks, Henri -- Thanks, Manjula. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Code Coverage Results for 10.4.1.3
Hi Manjula! I was able to fix the problem with linking the source-code, so now the site I mentioned before shows correct and complete results. To summarize and compare with your results: OVERALL COVERAGE SUMMARY -- all classes: 90% (1264/1397) Method : 75% (16948/22513) Block : 73% (479495/660441) Line : 71% (100760/141054) OVERALL STATS SUMMARY total packages: 89 total executable files: 1280 total classes: 1397 total methods: 22513 total executable lines: 141054 So we see a couple of (general) differences: 1. In general you report higher numbers for the totals 2. In general I find higher numbers for coverage Can this be explained by just the differences in our jvm's (as different vendors) or should we investigate more? For my numbers I did a little workaround regarding the source-code: I used the source-code from the 10.4-branch and not the official 10.4.1.3 Thanks ! Henri Manjula Kutty wrote: Hi Henri I ran suites.all. I used my derby_tests policy (Actually the one which gives all permission). I ran it with jdk142, 15 and 16. I will be linking the full report to the wiki. Thanks Manjula On 5/6/08, *Henri van de Scheur* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Manjula Kutty wrote: OVERALL COVERAGE SUMMARY -- all classes: 87% (1226/1404) Method : 74% (16629/22556) Block : 69% (486715/704201) Line : 69% (101022.4/146764) OVERALL STATS SUMMARY total packages: 90 total executable files: 1286 total classes: 1404 total methods: 22556 total executable lines: 146764 -- Thanks, Manjula. Hi Manjula! What testsuite did you use and which jvm-versions? I used Emma to run with suitesAll on jvm1.4, jvm1.5 and jvm1.6 (both 32- and 64-mode). Results can be found here: http://dbtg.thresher.com/derby/test/10.4.1.3_RC/Emma.html Unfortunately I have had some problems linking the source-code to these reports, but I plan to do that within the next 24 hours (if svn allows me). Thanks, Henri
Re: Code Coverage Results for 10.4.1.3
Manjula Kutty wrote: OVERALL COVERAGE SUMMARY -- all classes: 87% (1226/1404) Method : 74% (16629/22556) Block : 69% (486715/704201) Line : 69% (101022.4/146764) OVERALL STATS SUMMARY total packages: 90 total executable files: 1286 total classes: 1404 total methods: 22556 total executable lines: 146764 -- Thanks, Manjula. Hi Manjula! What testsuite did you use and which jvm-versions? I used Emma to run with suitesAll on jvm1.4, jvm1.5 and jvm1.6 (both 32- and 64-mode). Results can be found here: http://dbtg.thresher.com/derby/test/10.4.1.3_RC/Emma.html Unfortunately I have had some problems linking the source-code to these reports, but I plan to do that within the next 24 hours (if svn allows me). Thanks, Henri -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 651970S1 - Sun DBTG
Again, no tests run due to svn-problems. Looks OK today! Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 651970S1/2008-04-27 18:01:09 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll vista-64 NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-651970S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/651970S1_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-651970S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/651970S1_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-651970S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/651970S1_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/651970S1.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - Daily 651633S1 - Sun DBTG
Due to svn-trouble last night. no tests were run. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 651633S1/2008-04-25 18:01:08 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll vista-64 NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-651633S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/651633S1_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-651633S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/651633S1_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-651633S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/651633S1_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/651633S1.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - Daily 650922S1 - Sun DBTG
Due to svn-trouble last evening, the build-process took more than 2 hours and no tests were run. Today everything seems to run as expected. Since 10.4-testing is finished, nightly testing is run on most platforms again, including nightly testing on 10.4. Thanks! Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 650922S1/2008-04-23 18:01:00 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll vista-64 NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-650922S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/650922S1_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-650922S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/650922S1_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-650922S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/650922S1_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/650922S1.txt ( All results in http://dbtg.thresher.com/derby/test/ )
JIRA-issues without component set
I have defined a filter showing the number of Jira-issues lacking a component (see list below). The number of such issues has increased the last couple of weeks. Unfortunately I do not have the privilege to be able to categorize these and set the right component. I would like to ask the community to have a look at this list and categorize these issues with a component. Thank you! Henri Issue Subscription Filter: No components in Derby (22 issues) Subscriber: scheur Key Summary DERBY-3635 Cannot build SELECT LIST expressions involving row_number() https://issues.apache.org/jira/browse/DERBY-3635 DERBY-3634 Cannot use row_number() in ORDERY BY clause https://issues.apache.org/jira/browse/DERBY-3634 DERBY-3630 Odd assymetry in interaction of unique and not null constraints https://issues.apache.org/jira/browse/DERBY-3630 DERBY-3628 ij should show continuation marker even after entering whitespace https://issues.apache.org/jira/browse/DERBY-3628 DERBY-3626 Issue with bracketed SQL comments on a remote database connection from ij https://issues.apache.org/jira/browse/DERBY-3626 DERBY-3621 Hibernate. Derby uses type 'text' as clob(255) instead of long varchar https://issues.apache.org/jira/browse/DERBY-3621 DERBY-3613 SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2 https://issues.apache.org/jira/browse/DERBY-3613 DERBY-3605 Remove restriction If there is an index defined on the table, the table can be renamed. https://issues.apache.org/jira/browse/DERBY-3605 DERBY-3593 ErrorCode 3 when quering a select with 'having' clause and named tables with aliases for selected fields https://issues.apache.org/jira/browse/DERBY-3593 DERBY-3523 sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts https://issues.apache.org/jira/browse/DERBY-3523 DERBY-3484 build fails if compile.classpath is set to the same value as jsr169compile.classpath https://issues.apache.org/jira/browse/DERBY-3484 DERBY-3473 write test cases to test locking during tree operation https://issues.apache.org/jira/browse/DERBY-3473 DERBY-3471 Report meaningful error message when trying to use a connection to a database that has been shutdown https://issues.apache.org/jira/browse/DERBY-3471 DERBY-3464 NPE is seemingly simple query https://issues.apache.org/jira/browse/DERBY-3464 DERBY-3453 The PublicAPI class should belong to org.apache.derby.iapi.jdbc as it handles creation of SQLException https://issues.apache.org/jira/browse/DERBY-3453 DERBY-3452 ShutdownException and ErrorStringBuilder classes do not belong to the services context module https://issues.apache.org/jira/browse/DERBY-3452 DERBY-3451 Remove dependency between StandardException class and org.apache.derby.impl.jdbc classes. https://issues.apache.org/jira/browse/DERBY-3451 DERBY-3450 Reduce module dependencies in Derby https://issues.apache.org/jira/browse/DERBY-3450 DERBY-3405 Examine the possibility of implementing Derby modules as OSGI bundles https://issues.apache.org/jira/browse/DERBY-3405 DERBY-3402 Publish Japanese translated manual at documentation page. https://issues.apache.org/jira/browse/DERBY-3402 DERBY-3360 Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short) https://issues.apache.org/jira/browse/DERBY-3360 DERBY-3344 Error in testNegValueSupportedLogRecord in ugrade test - caused by EOF Exception in store in 10.3 https://issues.apache.org/jira/browse/DERBY-3344
[TESTRESULTS] Report for 10.4.1.3
Testresults for 10.4.1.3 are published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on up to 28 different OS platforms. A summary-report will be published here: http://dbtg.thresher.com/derby/test/10.4.1.3_RC/PublicTestReport.html I will also update http://wiki.apache.org/db-derby/TenFourPlatformTesting with these 10.4.1.3 test results. Thanks Henri
Re: [VOTE] 10.4.1.3 release candidate
[EMAIL PROTECTED] wrote: Please test and vote on the 10.4.1.3 release candidate, available at: http://people.apache.org/~dyre/derby-10.4.1.3-RC/ +1 -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
[TESTRESULTS] Report for 10.4.1.2
Testresults for 10.4.1.2 are published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on up to 28 different OS platforms. A summary-report will be published here: http://dbtg.thresher.com/derby/test/10.4.1.2_RC/PublicTestReport.html I have also updated http://wiki.apache.org/db-derby/TenFourPlatformTesting with these 10.4.1.2 test results. Thanks Henri PS: Results for 10.4.1.3 will be published tomorrow
[jira] Closed: (DERBY-1750) encryption/stress.multi fails with FatalException: XJ001: Java exception: ': java.lang.AbstractMethodError'. on Linux and Windows XP
[ https://issues.apache.org/jira/browse/DERBY-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-1750. -- I agree with Knut Anders. If this should happen again, the issue can be reopened. encryption/stress.multi fails with FatalException: XJ001: Java exception: ': java.lang.AbstractMethodError'. on Linux and Windows XP Key: DERBY-1750 URL: https://issues.apache.org/jira/browse/DERBY-1750 Project: Derby Issue Type: Bug Components: Regression Test Failure Affects Versions: 10.2.1.6 Environment: 2 X AMD Opteron(tm) Processor 244: 1792.052 MHz, 1024 KB cache. 2055844 kB Total Memory. Red Hat Enterprise Linux AS release 4 (Nahant Update 3) 64bits Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 GNU/Linux -- Java Information -- Java Version:1.6.0-rc Java Vendor: Sun Microsystems Inc. Java home: /usr/local/java/jdk1.6.0_b95/jre Java classpath: /export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/junit.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/dbprocedures.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jmxremote.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/javadbtests.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/Dots.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/mail.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/activation.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/Perfmon.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jakarta-oro-2.0.8.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/commons-logging.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jagops.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jdmkrt.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/db2jcc_license_c.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jet.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jetbatch.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/db2jcc.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jag.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jagclient.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jagutils.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/GenCfg.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jmxremote_optional.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/jmx.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/hadbjdbc4.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyTesting.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derby.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_zh_TW.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbytools.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_ko_KR.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_zh_CN.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_es.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_de_DE.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_ja_JP.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbynet.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_pt_BR.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyclient.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_fr.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyrun.jar:/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyLocale_it.jar: OS name: Linux OS architecture: i386 OS version: 2.6.9-34.ELsmp Java user name: jaguser Java user home: /home/jaguser Java user dir: /export/home/tmp/jagtmp/autoderbyN_regression/encryption_6/log java.specification.name: Java Platform API Specification java.specification.version: 1.6 - Derby Information JRE - JDBC: Java SE 6 - JDBC 4.0 [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derby.jar] 10.2.1.0 beta - (430903) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbytools.jar] 10.2.1.0 beta - (430903) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbynet.jar] 10.2.1.0 beta - (430903) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyclient.jar] 10.2.1.0 beta - (430903) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test
[TESTRESULTS] Report for 10.4.1.1
Testresults for 10.4.1.1 are published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on up to 27 different OS platforms. A summary-report will be published here: http://dbtg.thresher.com/derby/test/10.4.1.1_RC/TestReport.html I have also updated http://wiki.apache.org/db-derby/TenFourPlatformTesting with these 10.4.1.1 test results. Thanks Henri
Re: executeQuery hangs
Hi Radovan! Just a shot in the dark, since I do not know what kind of Windows you run. But if it is Vista, is it possible your installation was upgraded with SP1 last Friday? In that case your firewall-rules probably have changed and you have to grant some permissions one more time. I do not see the correlation with your problem, but only because it happened 'suddenly'. Henri Radovan Kobularcik wrote: Hello, I have a java swing application comunicating with Derby 10.1.2.6 DB through JDBC. Since friday one of the application part stoped to work as it cannot get data from database. I found that the last operation is executeQuery invoked on prepared statement. It stops at this point, no another activity (I'm not absolutely sure there is no exception (90%). App just waits for data from DB endlessly (90%)). Facts: - everything works fine when application is launched from windows server (= derby server), problem is when app is invoked from clients (windows net - server clients) - all sql queries from DB before failure point work (abount 10 queries) - these queries are invoked in the same way as the problematic one. - update of database to version 10.2.2.0 and 10.3.2.1 didn't help - derby trace shows that derby server received sql and there is also packet in trace file containing correct return data. - problematic query (select) is imho big but simple (select from 1 view, it has 800 bytes, size of return data I found in trace file is 27kB) - derby check_table function returned 1 (ok) Later on we found that installing application (also with derby db) from scratch to another server and copying old DB files (whole db dir) onto the new server helped. Doing this with the old server to the original directory didn't help. What says it is derby problem: - activity stops at prepStatement.executeQuery() What says it is Windows net problem: - app works when launched from server machine, doesn't when launched from clients - app works when reinstalled to another server - app doesn't work when reinstalled to original server to the same directory Now I'm not sure this is problem of derby or application. Could it be problem of Windows? (security, net). Does anybody have same problem? What should I check to find where the problem is? Thank you, Rado -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: [VOTE] V. Narayanan as a committer
Rick Hillegas wrote: Please vote on whether we should make V. Narayanan a Derby committer. The polls close at 5:00 pm San Francisco time on Thursday April 10. +1 Henri
Re: [VOTE] Jørgen Løland as a committ er
+1 Rick Hillegas wrote: Please vote on whether we should make Jørgen Løland a Derby committer. The polls close at 5:00 pm San Francisco time on Thursday April 10.
Changes in nightly testsuites
As of today, I have implemented some changes in the testsuites to be run in our daily testruns. For jvm1.6: 1. We no longer run all separate subsuites of derbyall 2. Added following suites, which are not part of suitesAll: * org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversClientTest org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversAllTest So we will now run the following testsuites: demoSuite compatibility derbyall jdbcapiAutoLoad jdbcapiJDBCDriversAll jdbcapiJDBCDriversClient jdbcapiJDBCDriversEmbedded replicationSuite suitesAll For jvm1.4 and jvm1.5, no changes were made. demosuite is still run as a separate suite, as a kind of a sanity check without using much time. Although replicationSuite now also is run as part of suitesAll, we keep it as a separate suite to be run to help the developers working on this. Thank you! Henri
Re: 10.4 branch test results from dbtg.thresher.com - which are ready?
I just posted a mail about testresults and together with Ole's answer, I hope this answers your questions. Thanks! Henri Mike Matrigali wrote: Henri van de Scheur wrote: Thank you Mike pointing this out! Due to Eastern holidays, things have got some delays. But I will make both this report and fill out the platformresults on the wiki - probably tomorrow. But we thought it might be useful to the community to already post results as soon as we had them, not realizing the rest that had to be filled out, taking more time than planned. So sorry for this! Machines used for release-testing have been reallocated to nightly runs as from last Tuesday. Unfortunately the 10.4 branch was not tested yesterday, due to some svn-problems. For trunk this was just finished before testing started, except for runs on sparc. I hope this will be in place again today. So all links should be functioning, at least from the beginning of next week, and probably tomorrow. Once again: thanks for your attention! Henri It is as expected, no apologies necessary -- I appreciate any info that gets posted and already the info there has helped get a feel of the state of the 10.4 line. When you think everything should be working just let me know and I can test it out. I know sometimes things look good from the inside but there are problems only visible from outside. Work is progressing on getting ibm 10.4 results posted also, but encountering non derby related issues and working through them. Mike Matrigali wrote: Some of the links from the public test post page for 10.4 at http://dbtg.thresher.com/derby/test/ are not working. I am sure this is new given that the release is just coming together, so just wondering if those maintaining this are already aware. I can report more in detail if that is useful. For instance in the 10.4.1.0 BETA1 line: Summary is broken: http://dbtg.thresher.com/derby/test/10.4.1.0_BETA1/TestReport.html - not tinderbox test link does not work - maybe not running yet? -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 637159 - Sun DBTG
Some of the machines used for these tests are now in use for testing the 10.4 beta. The coming period some of the platforms here will not be tested daily. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 637159/2008-03-14 18:01:10 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0274274 083.27% derbyall F:1,E:01045710456 0 1453.21% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0274274 077.40% derbyall F:1,E:01045710456 0 1735.25% suitesAll solN+1 0274274 0 100.25% derbyall F:1,E:01045710456 0 188.40% suitesAll sparc 0274274 067.50% derbyall F:1,E:01045710456 0 368.94% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-637159.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/637159_bySig.html *Jvm: 1.5* lin 0275275 081.23% derbyall F:1,E:087378736 0 1023.95% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0275275 079.82% derbyall F:3,E:087378734 0 861.04% suitesAll solN+1 0275275 089.85% derbyall F:1,E:087378736 0 813.38% suitesAll sparc 0275275 068.64% derbyall F:1,E:087378736 0 705.72% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-637159.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/637159_bySig.html *Jvm: 1.4* lin 0272272 282.00% derbyall 085858585 0 916.72% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0272272 278.72% derbyall 085858585 0 690.24% suitesAll solN+1 0272272 289.37% derbyall 085858585 0 752.46% suitesAll sparc 0272272 267.55% derbyall 085858585 0 710.92% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-637159.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/637159_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/637159.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Question about collatedSuite()
Kathey Marsden wrote: I noticed in CollationTest.collatedSuite() we run DatabaseMetaDataTest, BatchUpdateTest, GroupByExpressionTest, and UpdateableResultSetTest for each of four locales. I wonder if that really adds a lot of coverage or if it would be sufficient to run them with just one of the locales. Thoughts? It adds a fair amount of time to lang._Suite. Kathey I expect the coverage to be the same, but to get certainty you could verify this by using 'emma-single' (http://wiki.apache.org/db-derby/CodeCoverageWithEMMA) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 636416 - Sun DBTG
suitesAll was hanging on all platforms, also causing problems for subsequent tests. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 636416/2008-03-12 18:01:12 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0274274 081.64% derbyall NA NA NANA suitesAll sles 0274274 071.64% derbyall NA NA NANA suitesAll sol 0274274 076.76% derbyall NA NA NANA suitesAll solN+1 0274274 098.82% derbyall NA NA NANA suitesAll sparc 0274274 066.99% derbyall NA NA NANA suitesAll vista 0274274 093.98% derbyall NA NA NANA suitesAll w2003 0274274 097.94% derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-636416.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/636416_bySig.html *Jvm: 1.5* lin 0275275 080.72% derbyall NA NA NANA suitesAll sles 1275274 072.76% derbyall NA NA NANA suitesAll sol 0275275 080.18% derbyall NA NA NANA suitesAll solN+1 0275275 090.39% derbyall NA NA NANA suitesAll sparc 0275275 068.29% derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-636416.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/636416_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-636416.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/636416_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/636416.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - Daily 635600 - Sun DBTG
Platform 'linN+1' has become 'lin', meaning we no longer run on Red Hat AS 4 but from now on only on RHAS 5 (becoming 'lin'). Sorry, I should have informed about this before: this was activated last week. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 635600/2008-03-10 18:01:41 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0274274 081.63% derbyall 01045410454 0 1376.82% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles 0274274 071.26% derbyall 01045410454 0 908.02% suitesAll sol 0274274 075.21% derbyall 01045410454 0 1629.17% suitesAll solN+1 0274274 098.58% derbyall 01045410454 0 175.80% suitesAll sparc 0274274 066.37% derbyall 01045410454 0 367.23% suitesAll vista 0274274 094.35% derbyall 093459345 067.95% suitesAll w2003 0274274 098.57% derbyall F:4,E:71618891169 041.46% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-635600.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/635600_bySig.html *Jvm: 1.5* lin 0275275 080.53% derbyall 087348734 0 1018.25% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles 0275275 071.48% derbyall 087348734 0 572.72% suitesAll sol 0275275 079.34% derbyall 087348734 0 849.19% suitesAll solN+1 0275275 089.38% derbyall 087348734 0 810.32% suitesAll sparc 0275275 067.60% derbyall 087348734 0 706.49% suitesAll vista 0275275 072.17% derbyall 076257625 0 409.69% suitesAll w2003 0275275 075.76% derbyall 076257625 0 265.52% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-635600.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/635600_bySig.html *Jvm: 1.4* lin 0272272 281.64% derbyall 085828582 0 904.59% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles 0272272 273.37% derbyall 085828582 0 529.96% suitesAll sol 0272272 278.49% derbyall 085828582 0 698.45% suitesAll solN+1 0272272 290.14% derbyall 085828582 0 752.08% suitesAll sparc 0272272 267.68% derbyall 085828582 0 712.83% suitesAll vista 0272272 271.46% derbyall 074737473 0 398.30% suitesAll w2003 0272272 276.43% derbyall 074777477 0 255.38% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-635600.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/635600_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/635600.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Daily testing on branch 10.3 to be replaced by 10.4
From this evening on, daily testing on branch 10.3 will be stopped and replaced by daily testing on branch 10.4. Results will be reported under http://dbtg.thresher.com/derby/test/ -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 635013 - Sun DBTG
On most platforms suitesAll was hanging and causing the machines to get in a state not able to run the next testbatches. This is now being investigated and we hope to be able to start a daily tests tonight with better results. So sorry for the inconvenience! Especially when such things happen tin a weekend, it has a much bigger impact. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 635013/2008-03-08 18:01:05 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 1274273 094.12% derbyall 01041610416 0 1593.56% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0274274 0 114.40% derbyall 01041610416 0 1802.34% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-635013.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/635013_bySig.html *Jvm: 1.5* lin 1275274 086.36% derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0275275 080.20% derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-635013.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/635013_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-635013.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/635013_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/635013.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: {VOTE] Kim Haase as a committer
Rick Hillegas wrote: Please vote on whether we should make Kim Haase a committer. The vote will close at 5:00 pm San Francisco time on Monday March 10. Kim has made an outstanding contribution to Derby's documentation effort. With commit privileges, she will be even more effective. Regards, -Rick +1 -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 630637 - Sun DBTG
And although all systems came online again, some services were not available right away, causing no tests to be started. I hope and expect this to be solved for the next testcycle. Henri Henri van de Scheur wrote: Due to a power outage, all tests were aborted last night. Sorry for any inconvenience! Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 630637/2008-02-24 18:01:03 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0271271 071.85% derbyall NA NA NANA suitesAll linN+1 1271270 0 105.64% derbyall NA NA NANA suitesAll sles 0271271 070.89% derbyall NA NA NANA suitesAll sol 0271271 075.98% derbyall NA NA NANA suitesAll solN+1 0271271 098.97% derbyall NA NA NANA suitesAll sparc 0271271 065.61% derbyall NA NA NANA suitesAll vista 0271271 093.01% derbyall 091809180 066.35% suitesAll w2003 0271271 094.41% derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-630637.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/630637_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-630637.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/630637_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-630637.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/630637_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/630637.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 630637 - Sun DBTG
Due to a power outage, all tests were aborted last night. Sorry for any inconvenience! Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 630637/2008-02-24 18:01:03 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0271271 071.85% derbyall NA NA NANA suitesAll linN+1 1271270 0 105.64% derbyall NA NA NANA suitesAll sles 0271271 070.89% derbyall NA NA NANA suitesAll sol 0271271 075.98% derbyall NA NA NANA suitesAll solN+1 0271271 098.97% derbyall NA NA NANA suitesAll sparc 0271271 065.61% derbyall NA NA NANA suitesAll vista 0271271 093.01% derbyall 091809180 066.35% suitesAll w2003 0271271 094.41% derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-630637.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/630637_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-630637.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/630637_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-630637.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/630637_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/630637.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Commented: (DERBY-2872) Add Replication functionality to Derby
[ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571330#action_12571330 ] Henri van de Scheur commented on DERBY-2872: Thanks a lot Jørgen for your quick and descriptive replies! I regard all of my questions answered, apart from the last one, but that was more due to a bad formulated question. I will try to explain it through an example. Especially the fact having '1 Master, 1 Slave', reduces a lot of possible failure scenarios and makes it a lot easier. I just hadn't interpreted the spec this way. Limited network communication to only 1 single socket, also limits possible failure scenarios. So to question 9. Let's say that Instance I1 is not able to send log for database D1 to the slave in Instance I2 at the required pace. I1 will then try to increase the speed of log shipment. The latter might lead to reduced capacity in receiving log from Instance I2 and database D2. This then might lead to increasing speed of log shipment from instance I2, again leading to the same symptom: reduced capacity of receiving log shipments from Instance I1, etc. I hope this example makes my point more clear. But I guess response times will increase avoiding this situation. Add Replication functionality to Derby -- Key: DERBY-2872 URL: https://issues.apache.org/jira/browse/DERBY-2872 Project: Derby Issue Type: New Feature Components: Replication Affects Versions: 10.4.0.0 Reporter: Jørgen Løland Assignee: Jørgen Løland Attachments: master_classes_1.pdf, poc_master_v2.diff, poc_master_v2.stat, poc_master_v2b.diff, poc_slave_v2.diff, poc_slave_v2.stat, poc_slave_v2b.diff, poc_slave_v2c.diff, proof-of-concept_v2b-howto.txt, proof_of_concept_master.diff, proof_of_concept_master.stat, proof_of_concept_slave.diff, proof_of_concept_slave.stat, replication_funcspec.html, replication_funcspec_v2.html, replication_funcspec_v3.html, replication_funcspec_v4.html, replication_funcspec_v5.html, replication_funcspec_v6.html, replication_funcspec_v7.html, replication_funcspec_v8.html, replication_funcspec_v9.html, replication_script.txt, slave_classes_1.pdf It would be nice to have replication functionality to Derby; many potential Derby users seem to want this. The attached functional specification lists some initial thoughts for how this feature may work. Dag Wanvik had a look at this functionality some months ago. He wrote a proof of concept patch that enables replication by copying (using file system copy) and redoing the existing Derby transaction log to the slave (unfortunately, I can not find the mail thread now). DERBY-2852 contains a patch that enables replication by sending dedicated logical log records to the slave through a network connection and redoing these. Replication has been requested and discussed previously in multiple threads, including these: http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/[EMAIL PROTECTED] http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2872) Add Replication functionality to Derby
[ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur updated DERBY-2872: --- Comment: was deleted Add Replication functionality to Derby -- Key: DERBY-2872 URL: https://issues.apache.org/jira/browse/DERBY-2872 Project: Derby Issue Type: New Feature Components: Replication Affects Versions: 10.4.0.0 Reporter: Jørgen Løland Assignee: Jørgen Løland Attachments: master_classes_1.pdf, poc_master_v2.diff, poc_master_v2.stat, poc_master_v2b.diff, poc_slave_v2.diff, poc_slave_v2.stat, poc_slave_v2b.diff, poc_slave_v2c.diff, proof-of-concept_v2b-howto.txt, proof_of_concept_master.diff, proof_of_concept_master.stat, proof_of_concept_slave.diff, proof_of_concept_slave.stat, replication_funcspec.html, replication_funcspec_v2.html, replication_funcspec_v3.html, replication_funcspec_v4.html, replication_funcspec_v5.html, replication_funcspec_v6.html, replication_funcspec_v7.html, replication_funcspec_v8.html, replication_funcspec_v9.html, replication_script.txt, slave_classes_1.pdf It would be nice to have replication functionality to Derby; many potential Derby users seem to want this. The attached functional specification lists some initial thoughts for how this feature may work. Dag Wanvik had a look at this functionality some months ago. He wrote a proof of concept patch that enables replication by copying (using file system copy) and redoing the existing Derby transaction log to the slave (unfortunately, I can not find the mail thread now). DERBY-2852 contains a patch that enables replication by sending dedicated logical log records to the slave through a network connection and redoing these. Replication has been requested and discussed previously in multiple threads, including these: http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/[EMAIL PROTECTED] http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2872) Add Replication functionality to Derby
[ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571022#action_12571022 ] Henri van de Scheur commented on DERBY-2872: I have a few comments/questions to the Functional Specification for Derby Replication - rev. 9.0. Great to see a chapter 'Handling Failure Scenarios', but as stated here, there are numerous failure scenarios which can be encountered. As a follow-up, I would like to raise the following questions/comments: 1. Would be nice to also describe a scenario where the slave Derby instance crashes 2. Please confirm the following statement: 'Since the slave database is in recovery-mode, no data in the slave database can be changed at all by any means'. If this wouldn't be the case, a lot of consistency-problems and scenarios should be taken into account. 3. Is the relation Master-Slave really an N:M-relation and if so, are N and/or M somehow limited? 4. Master has still connection with Slave, but for some reason the Slave does not process the received logrecords: will this be seen as 'unexpected failure'? 5. Network issue: what to do in case of missing packages? 6. Network issue: will a multipath-configuration be supported? This will lead to a Slave receiving records in a wrong sequence 7. Network issue: multiple-network-interfaces: question as for 6). In addition: special scenario(s) if one such interface is dropped? 8. If 1 Master replicates to 2 different Slaves and one of these Slaves has a lower 'bandwidth' to receive/process the logs, will this one then determine the total (replication)transactional processes, thus also limit sending to the other Slave? 9. If Derby instance I1 contains database D1 as Master, database D2 as Slave, instance I2 contains the same but with opposite roles: isn't there a big risk for a 'dead' race in case of problems with main memory log buffer? Thanks! Add Replication functionality to Derby -- Key: DERBY-2872 URL: https://issues.apache.org/jira/browse/DERBY-2872 Project: Derby Issue Type: New Feature Components: Replication Affects Versions: 10.4.0.0 Reporter: Jørgen Løland Assignee: Jørgen Løland Attachments: master_classes_1.pdf, poc_master_v2.diff, poc_master_v2.stat, poc_master_v2b.diff, poc_slave_v2.diff, poc_slave_v2.stat, poc_slave_v2b.diff, poc_slave_v2c.diff, proof-of-concept_v2b-howto.txt, proof_of_concept_master.diff, proof_of_concept_master.stat, proof_of_concept_slave.diff, proof_of_concept_slave.stat, replication_funcspec.html, replication_funcspec_v2.html, replication_funcspec_v3.html, replication_funcspec_v4.html, replication_funcspec_v5.html, replication_funcspec_v6.html, replication_funcspec_v7.html, replication_funcspec_v8.html, replication_funcspec_v9.html, replication_script.txt, slave_classes_1.pdf It would be nice to have replication functionality to Derby; many potential Derby users seem to want this. The attached functional specification lists some initial thoughts for how this feature may work. Dag Wanvik had a look at this functionality some months ago. He wrote a proof of concept patch that enables replication by copying (using file system copy) and redoing the existing Derby transaction log to the slave (unfortunately, I can not find the mail thread now). DERBY-2852 contains a patch that enables replication by sending dedicated logical log records to the slave through a network connection and redoing these. Replication has been requested and discussed previously in multiple threads, including these: http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/[EMAIL PROTECTED] http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2872) Add Replication functionality to Derby
[ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571021#action_12571021 ] Henri van de Scheur commented on DERBY-2872: I have a few comments/questions to the Functional Specification for Derby Replication - rev. 9.0. Great to see a chapter 'Handling Failure Scenarios', but as stated here, there are numerous failure scenarios which can be encountered. As a follow-up, I would like to raise the following questions/comments: 1. Would be nice to also describe a scenario where the slave Derby instance crashes 2. Please confirm the following statement: 'Since the slave database is in recovery-mode, no data in the slave database can be changed at all by any means'. If this wouldn't be the case, a lot of consistency-problems and scenarios should be taken into account. 3. Is the relation Master-Slave really an N:M-relation and if so, are N and/or M somehow limited? 4. Master has still connection with Slave, but for some reason the Slave does not process the received logrecords: will this be seen as 'unexpected failure'? 5. Network issue: what to do in case of missing packages? 6. Network issue: will a multipath-configuration be supported? This will lead to a Slave receiving records in a wrong sequence 7. Network issue: multiple-network-interfaces: question as for 6). In addition: special scenario(s) if one such interface is dropped? 8. If 1 Master replicates to 2 different Slaves and one of these Slaves has a lower 'bandwidth' to receive/process the logs, will this one then determine the total (replication)transactional processes, thus also limit sending to the other Slave? 9. If Derby instance I1 contains database D1 as Master, database D2 as Slave, instance I2 contains the same but with opposite roles: isn't there a big risk for a 'dead' race in case of problems with main memory log buffer? Thanks! Add Replication functionality to Derby -- Key: DERBY-2872 URL: https://issues.apache.org/jira/browse/DERBY-2872 Project: Derby Issue Type: New Feature Components: Replication Affects Versions: 10.4.0.0 Reporter: Jørgen Løland Assignee: Jørgen Løland Attachments: master_classes_1.pdf, poc_master_v2.diff, poc_master_v2.stat, poc_master_v2b.diff, poc_slave_v2.diff, poc_slave_v2.stat, poc_slave_v2b.diff, poc_slave_v2c.diff, proof-of-concept_v2b-howto.txt, proof_of_concept_master.diff, proof_of_concept_master.stat, proof_of_concept_slave.diff, proof_of_concept_slave.stat, replication_funcspec.html, replication_funcspec_v2.html, replication_funcspec_v3.html, replication_funcspec_v4.html, replication_funcspec_v5.html, replication_funcspec_v6.html, replication_funcspec_v7.html, replication_funcspec_v8.html, replication_funcspec_v9.html, replication_script.txt, slave_classes_1.pdf It would be nice to have replication functionality to Derby; many potential Derby users seem to want this. The attached functional specification lists some initial thoughts for how this feature may work. Dag Wanvik had a look at this functionality some months ago. He wrote a proof of concept patch that enables replication by copying (using file system copy) and redoing the existing Derby transaction log to the slave (unfortunately, I can not find the mail thread now). DERBY-2852 contains a patch that enables replication by sending dedicated logical log records to the slave through a network connection and redoing these. Replication has been requested and discussed previously in multiple threads, including these: http://mail-archives.apache.org/mod_mbox/db-derby-user/200504.mbox/[EMAIL PROTECTED] http://www.nabble.com/Does-Derby-support-Transaction-Logging---t2626667.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Regression Test Report - Daily 628123 - Sun DBTG
Sorry, but runs with 1.4 were aborted due to some misconfiguration in our environment. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 628123/2008-02-15 18:01:11 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0271271 071.88% derbyall 01022610226 0 1374.39% suitesAll linN+1 0271271 0 103.34% derbyall 01022610226 0 112.34% suitesAll sles 0271271 071.25% derbyall 01022610226 0 860.28% suitesAll sol 0271271 075.77% derbyall 01022610226 0 1650.90% suitesAll solN+1 0271271 096.82% derbyall 01022610226 0 203.20% suitesAll sparc 0271271 065.48% derbyall 01022610226 0 359.44% suitesAll vista 0271271 093.14% derbyall 091739173 067.04% suitesAll w2003 0271271 095.87% derbyall 091739173 0 132.24% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-628123.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/628123_bySig.html *Jvm: 1.5* lin 0272272 071.35% derbyall 085088508 0 888.59% suitesAll linN+1 0272272 097.60% derbyall 085088508 0 116.29% suitesAll sles 0272272 070.50% derbyall 085088508 0 575.79% suitesAll sol 0272272 079.52% derbyall 085088508 0 851.60% suitesAll solN+1 0272272 088.07% derbyall 085088508 0 807.11% suitesAll sparc 0272272 066.28% derbyall 085088508 0 697.26% suitesAll vista 0272272 071.38% derbyall 074557455 0 395.15% suitesAll w2003 0272272 073.99% derbyall 074557455 0 258.12% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-628123.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/628123_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-628123.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/628123_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/628123.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 628359 - Sun DBTG
Sorry, but runs with 1.4 were aborted due to some misconfiguration in our environment. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 628359/2008-02-16 18:01:05 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0271271 072.05% derbyall 01022610226 0 1506.09% suitesAll linN+1 0271271 0 100.09% derbyall 01022610226 0 114.25% suitesAll sles 0271271 071.20% derbyall 01022610226 0 863.84% suitesAll sol 0271271 075.95% derbyall 01022610226 0 1470.18% suitesAll solN+1 0271271 097.26% derbyall 01022610226 0 190.26% suitesAll sparc 0271271 066.76% derbyall 01022610226 0 362.14% suitesAll vista 0271271 092.79% derbyall 091739173 063.25% suitesAll w2003 0271271 095.52% derbyall 091739173 0 132.98% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-628359.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/628359_bySig.html *Jvm: 1.5* lin 0272272 071.37% derbyall 085088508 0 882.69% suitesAll linN+1 0272272 098.00% derbyall 085088508 0 115.88% suitesAll sles 0272272 070.35% derbyall 085088508 0 566.90% suitesAll sol 0272272 079.47% derbyall 085088508 0 852.61% suitesAll solN+1 0272272 088.20% derbyall 085088508 0 806.41% suitesAll sparc 0272272 066.32% derbyall 085088508 0 690.85% suitesAll vista 0272272 070.95% derbyall 074557455 0 395.69% suitesAll w2003 0272272 074.25% derbyall 074557455 0 256.92% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-628359.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/628359_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-628359.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/628359_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/628359.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
[jira] Commented: (DERBY-3359) The log shipper needs to be modified to vary the shipping intervals dynamically (based on load)
[ https://issues.apache.org/jira/browse/DERBY-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567656#action_12567656 ] Henri van de Scheur commented on DERBY-3359: Knut Anders Hatlen commented on DERBY-3359: Could we also make mf final? Then we would have caught the error at compile time. Good proposal. Fix committed as revision 620499. The log shipper needs to be modified to vary the shipping intervals dynamically (based on load) --- Key: DERBY-3359 URL: https://issues.apache.org/jira/browse/DERBY-3359 Project: Derby Issue Type: Sub-task Reporter: V.Narayanan Assignee: V.Narayanan Attachments: DynamicLogShipping_v1.diff, DynamicLogShipping_v1.stat, DynamicLogShipping_v2.diff, DynamicLogShipping_v2.stat, DynamicLogShipping_v3.diff, DynamicLogShipping_v3.stat, DynamicLogShipping_v4.diff, DynamicLogShipping_v4.stat -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2948) Reoccurrence of DERBY-2842: derbynet/testconnection.java fails with '...Connection refused: connect' expecting 'Connection refused'
[ https://issues.apache.org/jira/browse/DERBY-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-2948. -- No longer an issue Reoccurrence of DERBY-2842: derbynet/testconnection.java fails with '...Connection refused: connect' expecting 'Connection refused' --- Key: DERBY-2948 URL: https://issues.apache.org/jira/browse/DERBY-2948 Project: Derby Issue Type: Bug Components: Regression Test Failure Affects Versions: 10.3.1.4 Environment: derbyall fail * derbyall/derbynetmats/derbynetmats.fail:derbynet/testconnection.java derbyall fail * Generating report for RunSuite derbyall null null null true -- Java Information -- Java Version:1.5.0_07 Java Vendor: Sun Microsystems Inc. Java home: /usr/local/java/jdk1.5.0_07/jre Java classpath: /export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jet.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_ko_KR.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyrun.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_ja_JP.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbynet.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derby.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_zh_CN.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyclient.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_zh_TW.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_cs.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_es.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_fr.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_hu.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_it.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_pl.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbytools.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_ru.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyTesting.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_pt_BR.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbyLocale_de_DE.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jmx.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/javadbtesttools.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/activation.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jdmkrt.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/javadbtests.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/dbprocedures.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/Perfmon.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/mail.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jagops.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/GenCfg.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/hadbjdbc4.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jetapi.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/commons-logging.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/db2jcc.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jmxremote.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/db2jcc_license_c.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jakarta-oro-2.0.8.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/Dots.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jag.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jmxremote_optional.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/jetbatch.jar:/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/test/junit.jar: OS name: Linux OS architecture: i386 OS version: 2.6.16.21-0.8-smp Java user name: jaguser Java user home: /home/jaguser Java user dir: /export/home/tmp/jagtmp/autoderbyN_derbyall/derbyall_0/log java.specification.name: Java Platform API Specification java.specification.version: 1.5 - Derby Information JRE - JDBC: J2SE 5.0 - JDBC 3.0 [/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derby.jar] 10.3.1.2 - (556213) [/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib/derbytools.jar] 10.3.1.2 - (556213) [/export/home/tmp/jagtmp/autoderbyN_derbyall/install/lib
[jira] Closed: (DERBY-3029) Several broken links on Derby web-site
[ https://issues.apache.org/jira/browse/DERBY-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-3029. -- Thanks for working on this! Several broken links on Derby web-site -- Key: DERBY-3029 URL: https://issues.apache.org/jira/browse/DERBY-3029 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Assignee: Myrna van Lunteren Priority: Minor Attachments: Apache_Derby_LinkDoctorReport_20070905.htm, ApacheDerby_LinkDoctorReport.htm I have used an old tool (Astra Site Manager) to check for broken links on our website and several were reported. See the htm-report, which will be attached. I have done the same check from our documentation site, but will create a separate issue for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2899) Reoccurrence of DERBY-2434: HarnessJavaTest fails on UTF-8 locale.
[ https://issues.apache.org/jira/browse/DERBY-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-2899. -- Since Derby-957 was fixed and this was a duplicate, this one can also be closed. Reoccurrence of DERBY-2434: HarnessJavaTest fails on UTF-8 locale. -- Key: DERBY-2899 URL: https://issues.apache.org/jira/browse/DERBY-2899 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.3.1.4 Environment: Microsoft(R) Windows(R) Server 2003, - 5.2.3790 Service Pack 2 WindowsNT 2 5 Sun jvm 1.5.0_07-b03 Also seen on windows2000 and Windows Vista Reporter: Henri van de Scheur There was 1 failure: 1) statementJdbc20(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)junit.framework.ComparisonFailure: Output at line 3 expected:... parameter value '-1[,]000' for Statement.s... but was:... parameter value '-1[?]000' for Statement.s... at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:100) at org.apache.derbyTesting.functionTests.util.HarnessJavaTest.runTest(HarnessJavaTest.java:91) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:88) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) Also see logging under http://dbtg.thresher.com/derby/test/10.3.1.0_RC/jvm1.5/testing/testlog/w2003/548006-suitesAll_diff.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet
[ https://issues.apache.org/jira/browse/DERBY-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur closed DERBY-1585. -- Not seen anymore after week 2 when this was fixed derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet - Key: DERBY-1585 URL: https://issues.apache.org/jira/browse/DERBY-1585 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.2.1.6 Environment: -- Java Information -- Java Version:1.6.0-rc Java Vendor: Sun Microsystems Inc. Java home: /usr/local/java/jdk1.6.0_b91/jre Java classpath: test/junit.jar:test/dbprocedures.jar:test/jmxremote.jar:test/javadbtests.jar: test/Dots.jar:test/mail.jar:test/activation.jar:test/Perfmon.jar: test/jakarta-oro-2.0.8.jar:test/commons-logging.jar:test/jagops.jar: test/jdmkrt.jar:test/db2jcc_license_c.jar:test/jet.jar:test/jetbatch.jar: test/db2jcc.jar:test/jag.jar:test/jagclient.jar:test/jagutils.jar:test/GenCfg.jar: test/jmxremote_optional.jar:test/jmx.jar:test/hadbjdbc4.jar:derbyTesting.jar: derby.jar:derbyLocale_zh_TW.jar:derbytools.jar:derbyLocale_ko_KR.jar: derbyLocale_zh_CN.jar:derbyLocale_es.jar:derbyLocale_de_DE.jar:derbyLocale_ja_JP.jar: derbynet.jar:derbyLocale_pt_BR.jar:derbyclient.jar:derbyLocale_fr.jar:derbyrun.jar: derbyLocale_it.jar: OS name: Linux OS architecture: i386 OS version: 2.6.9-34.ELsmp java.specification.name: Java Platform API Specification java.specification.version: 1.6 - Derby Information JRE - JDBC: Java SE 6 - JDBC 4.0 [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derby.jar] 10.2.0.4 alpha - (423199) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbytools.jar] 10.2.0.4 alpha - (423199) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbynet.jar] 10.2.0.4 alpha - (423199) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/derbyclient.jar] 10.2.0.4 alpha - (423199) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/db2jcc_license_c.jar] 2.4 - (17) [/export/home/tmp/jagtmp/autoderbyN_regression/install/lib/test/db2jcc.jar] 2.4 - (17) -- - Locale Information - Current Locale : [English/United States [en_US]] Found support for locale: [de_DE] version: 10.2.0.4 alpha - (423199) Found support for locale: [es] version: 10.2.0.4 alpha - (423199) Found support for locale: [fr] version: 10.2.0.4 alpha - (423199) Found support for locale: [it] version: 10.2.0.4 alpha - (423199) Found support for locale: [ja_JP] version: 10.2.0.4 alpha - (423199) Found support for locale: [ko_KR] version: 10.2.0.4 alpha - (423199) Found support for locale: [pt_BR] version: 10.2.0.4 alpha - (423199) Found support for locale: [zh_CN] version: 10.2.0.4 alpha - (423199) Found support for locale: [zh_TW] version: 10.2.0.4 alpha - (423199) -- Reporter: Henri van de Scheur Assignee: Daniel John Debrunner Fix For: 10.3.2.2, 10.4.0.0 Attachments: close.diff, derby1585_diff.txt, derby1585_diff_v2.txt, derby1585_v1.diff, derby1585_v1.status, Main.java * Diff file derbyall/derbylang/procedureInTrigger.diff *** Start: procedureInTrigger jdk1.6.0-rc derbyall:derbylang 2006-07-19 13:52:20 *** 714a715,730 ERROR X0X95: Operation 'CREATE TRIGGER' cannot be performed on object 'T1' because there is an open ResultSet dependent on that object. ij --- delete a row. check that trigger is fired - procedure should be called once delete from t1 where i=10; 1 row inserted/updated/deleted ij --- check delete is successful select * from t1; I |B --- 5 |two 6 |four 8 |eight ij drop trigger select_from_trig_table; ERROR 42X94: TRIGGER 'SELECT_FROM_TRIG_TABLE' does not exist. ij --- use procedures which alter/drop trigger table and some other table create trigger alter_table_trig AFTER delete on t1 for each STATEMENT mode db2sql call alter_table_proc(); 716,732d731 ij --- delete a row. check that trigger is fired - procedure should be called once delete from t1 where i=10; selectRows - 1 arg - 1 rs 1 row inserted/updated/deleted ij --- check delete is successful select * from t1; I |B --- 5 |two 6 |four 8 |eight ij drop trigger select_from_trig_table
Re: PermGen space: OutOfMemoryError
Knut Anders Hatlen wrote: Kathey Marsden [EMAIL PROTECTED] writes: Has anyone ever seen a PermGen space:OutOfMemoryError running suites.All? I have been running the JUnit tests with -XX:MaxPermSize=128M for a long time because of this problem. Henri's regression tests also run with increased permgen size, according to this posting: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200707.mbox/[EMAIL PROTECTED] That is correct. We still run with this option as default. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
[jira] Created: (DERBY-3317) Document 'Apache Derby Issues in Jira' lacks descriptions for several components
Document 'Apache Derby Issues in Jira' lacks descriptions for several components Key: DERBY-3317 URL: https://issues.apache.org/jira/browse/DERBY-3317 Project: Derby Issue Type: Improvement Components: Documentation Environment: NA Reporter: Henri van de Scheur Priority: Minor Both the doc- and pdf-version of 'Apache Derby Issues in Jira' (http://db.apache.org/derby/binaries/FilingDerbyIssuesInJira.doc) lacks descriptions for the following components: Demos/Scripts Eclipse Plugin Javadoc Miscellaneous Network Client Newcomer Performance Regression Test Failure Replication Web Site I was trying to find out the difference between component 'Test' and 'Regression Test Failure', when I found a description for Test in this document. In other words I still haven't found a clear definition of the latter, although it looks like the latter should be used for nightly failures. Most of the other components are easy to understand, but 'Regression Test Failure' can be interpreted in different ways. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Regression Test Report - Daily 611233 - Sun DBTG
This report was created 'manually' after this automatic mail hadn't been send for a couple of days. Reason for this was a swap of machines and forgetting this reporting job to be moved. Sorry for the inconvenience! Results for the last days can be found under http://dbtg.thresher.com/derby/test/Daily I hope this mail will be send again automatically and with contents from tomorrow. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 611233/2008-01-11 18:01:49 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-611233.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/611233_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-611233.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/611233_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-611233.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/611233_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/611233.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: CTS
Ole Solberg wrote: Kathey Marsden wrote: I am curious, has anyone run CTS, the JDBC Certification Test Suite against 10.3.1.4 or 10.3.2.1 release candidate? For 10.3.2.1 JDBC 3.0 Compatibility Test Suite (CTS) was run on 3 platforms. See http://dbtg.thresher.com/derby/test/10.3.2.1_RC/TestReport.html / http://dbtg.thresher.com/derby/test/10.3.2.1_RC/AdditionalTests.html For 10.3.1.4 it was run on 6 platforms: http://dbtg.thresher.com/derby/test/10.3.1.4_RC/AdditionalTests.html Unfortunately, no runs on Solaris 10 succeeded after an OS-upgrade/reinstall. After this reinstallation there were some problems with privileges for the appserver. This has now been corrected, but comes too late for a rerun. But we have no reason to suspect any problems on these platforms. Thanks Kathey
Re: [VOTE] 10.3.2.1 release candidate
+1 See http://wiki.apache.org/db-derby/TenThreePlatformTesting for testing done. Henri Kathey Marsden wrote: Please test and vote on the 10.3.2.1 release candidate, available at: http://people.apache.org/~kmarsden/derby10.3.2.1.599110/ You can report platform testing results at: http://wiki.apache.org/db-derby/TenThreeTwoPlatformTesting Other testing results can be reported at http://wiki.apache.org/db-derby/DerbyTenThreeTwoRelease Polls will close Friday, December 7, 2007 5:00pm PST. Thanks Kathey
Re: [jira] Commented: (DERBY-3261) 'Empty right rows returned = 0' expected '... = 1' in lang/outerjoin.sql
I think this one is meant: http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/601833-derbyall_diff.txt Henri Mamta A. Satoor (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549567 ] Mamta A. Satoor commented on DERBY-3261: Olg, I tried going to http://clustra.norway.sun.com/~os136789/Apache/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/601833-derbyall_diff.txt to see the test results but looks like the url is incorrect. Could you please check if there is some typo in the url that you posted? thanks 'Empty right rows returned = 0' expected '... = 1' in lang/outerjoin.sql Key: DERBY-3261 URL: https://issues.apache.org/jira/browse/DERBY-3261 Project: Derby Issue Type: Bug Components: Regression Test Failure Affects Versions: 10.4.0.0 Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS 5.10 Generic_118855-14 JVM: Sun Microsystems Inc. 1.6.0_02-b05 Reporter: Ole Solberg Priority: Minor See http://clustra.norway.sun.com/~os136789/Apache/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/601833-derbyall_diff.txt Failure Details: * Diff file derbyall/derbylang/outerjoin.diff *** Start: outerjoin jdk1.6.0_02 derbyall:derbylang 2007-12-06 22:22:35 *** 1737 del Empty right rows returned = 1 1737a1737 Empty right rows returned = 0 Test Failed. *** End: outerjoin jdk1.6.0_02 derbyall:derbylang 2007-12-06 22:22:43 ***
[TESTRESULTS] Report for 10.3.2.1
Testresults for 10.3.2.1 RC2 have been published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on 20 different OS platforms. A summary-report has been published here: http://dbtg.thresher.com/derby/test/10.3.2.1_RC/TestReport.html I have also updated http://wiki.apache.org/db-derby/TenThreePlatformTesting with these 10.3.2.1 test results. In addition I added a row for 10.3.2.0, since the Longtermtest was started on that version. Thanks Henri
Re: Regression Test Report - Daily 599062 - Sun DBTG
As you might have understood, some platforms have been taken out of this pool to be used for testing the 10.3.2 They will return as soon as that testing has been finished. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 599062/2007-11-28 18:00:11 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0274274 072.28% derbyall F:0,E:11011910118 0 1161.30% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0274274 076.24% derbyall 01011910119 0 1439.61% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0274274 065.82% derbyall 01011910119 0 325.44% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 0274274 0 .% derbyall 090989098 0 222.45% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-599062.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/599062_bySig.html *Jvm: 1.5* lin 1275274 069.32% derbyall 084038403 0 809.31% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0275275 080.23% derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0275275 066.78% derbyall 084038403 0 622.47% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 0275275 074.43% derbyall 073827382 0 237.29% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-599062.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/599062_bySig.html *Jvm: 1.4* lin 0272272 272.93% derbyall 083518351 0 741.31% suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0272272 267.53% derbyall 083518351 0 631.45% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 0272272 2 .% derbyall 073307330 0 .% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-599062.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/599062_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/599062.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
[TESTRESULTS]LongTermTest on 10.3.1.4 finished
As planned the LongTermTest was running for about 3 months. As seen in this test before, there were just some deadlock-problems in the beginning (see http://dbtg.thresher.com/derby/longrun/JavaDB-10.3.1.4/logs/ATCJ3-2007-8-23-14-1-37-126.err , Tue Aug 28 01:31:09), but after that no issues have been observed. Description, details and graphs can be found at http://dbtg.thresher.com/derby/longrun/JavaDB-10.3.1.4/index.html -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Failure in lang/compressTable.sql with current 10.3 branch
Hi Bryan! I also see it in my daily tests on 10.3. Look for instance at http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.4/FailReports/596747_bySig.html It started to appear the 20th of November, so that might help? It appears on all platforms and under all jvm-versions. (see http://dbtg.thresher.com/derby/test/ - 10.3 Branch - daily) Henri Bryan Pendleton wrote: Hi all, I'm seeing a failure in lang/compressTable.sql with the current 10.3 branch. Is anyone else seeing this? The diff appears to involve a slight difference in the value of the last column in the SYS.SYSSTATISTICS catalog. Here's a snip from compressTable.tmpmstr: create index t2i1 on derby737table2(c1); 0 rows inserted/updated/deleted ij select * from sys.sysstatistics; STATID |REFERENCEID |TABLEID |CREATIONTIMESTAMP ||VALID|COLCOUNT |STATISTICS -- FILTERED-UUID|FILTERED-UUID|FILTERED-UUID|xxFILTERED-TIMESTAMPx|I|true |1 |numunique= And here's the equivalent section of my compressTable.out: create index t2i1 on derby737table2(c1); 0 rows inserted/updated/deleted ij select * from sys.sysstatistics; STATID |REFERENCEID |TABLEID |CREATIONTIMESTAMP ||VALID|COLCOUNT |STATISTICS - FILTERED-UUID|FILTERED-UUID|FILTERED-UUID|xxFILTERED-TIMESTAMPx|I|true |1 |numunique= 2 n This diff appears to occur in all the SYS.SYSSTATISTICS references in the DERBY-737 section of compressTable.sql. Does anyone have a suggestion as to what might be causing this? thanks, bryan
Re: 10.3.2 release. Not much time left
Daniel John Debrunner wrote: Kathey Marsden wrote: Just a reminder that you have until 5pm, PST, November 25 to checkin fixes for the 10.3.2 release. FYI I ran the junit tests using the latest version of 10.3 (from the branch) but taking derbyTesting.jar from the 10.3.1.4 release. I saw a number of failures (at least six I think). That potentially means a number of regressions, though it could be test issues, I know one (AutoloadTest) is a failure that existed at the time 10.3.1.4 was released. I'll re-run the same test and this time save the results to see if they are issues that should be investigated. Dan. Just FYI: I also run a daily test on the 10.3 branch, but as far as I can see this looks quite good: see 'Daily' under ' 10.3 Branch' at http://dbtg.thresher.com/derby/test/ But then everything is taken from the branch. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 594581 - Sun DBTG
This report was already send yesterday. Todays report was not generated. Due to a build-failure - caused by internal environmental issues - no tests were run. I hope this will be repaired for this evening. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 594581/2007-11-13 18:00:15 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0282282 072.71% derbyall F:0,E:197629761 0 1271.61% suitesAll linN+1 0282282 0 .% derbyall 097629762 0 .% suitesAll sles 0282282 071.65% derbyall 097629762 0 839.01% suitesAll sol 0282282 076.39% derbyall 097629762 0 1297.65% suitesAll solN+1 0282282 084.01% derbyall 097629762 0 1242.85% suitesAll sparc 0282282 066.77% derbyall 097629762 0 307.60% suitesAll vista 0282282 0 .% derbyall F:2,E:589078900 0 389.71% suitesAll w2003 0282282 0 .% derbyall F:2,E:589078900 0 215.31% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-594581.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/594581_bySig.html *Jvm: 1.5* lin 1283282 072.41% derbyall 080488048 0 777.75% suitesAll linN+1 0283283 0 .% derbyall 080488048 0 .% suitesAll sles 0283283 071.46% derbyall 080488048 0 506.43% suitesAll sol 0283283 081.42% derbyall 080488048 0 749.79% suitesAll solN+1 1283282 088.67% derbyall 080488048 0 704.88% suitesAll sparc 0283283 068.11% derbyall 080488048 0 588.97% suitesAll vista 0283283 072.05% derbyall F:2,E:571937186 0 357.09% suitesAll w2003 0283283 075.33% derbyall F:2,E:571937186 0 233.87% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-594581.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/594581_bySig.html *Jvm: 1.4* lin 0280280 273.53% derbyall 079967996 0 702.29% suitesAll linN+1 0280280 2 .% derbyall 079967996 0 .% suitesAll sles 0280280 270.66% derbyall 079967996 0 464.70% suitesAll sol 0280280 278.16% derbyall 079967996 0 599.84% suitesAll solN+1 0280280 289.59% derbyall 079967996 0 668.26% suitesAll sparc 0280280 267.78% derbyall 079967996 0 600.91% suitesAll vista 0280280 2 .% derbyall F:2,E:171417138 0 350.00% suitesAll w2003 0280280 2 .% derbyall F:2,E:171417138 0 .% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-594581.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/594581_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/594581.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: [jira] Resolved: (DERBY-3030) Several broken links on Derby documentation web-site
Thanks a lot Myrna! I hope to run a check again next week. Henri Myrna van Lunteren (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-3030. --- Resolution: Fixed Fix Version/s: 10.4.0.0 I've made what changes could be made in the 'current' doc source; what's left are entries in documentation for older releases, and I don't think it necessary to correct those old references... With revision 583347 I modified the main doc page's references to 10.2/pt_BR manuals. With revision 594451 I removed some extra characters from a link in the ja_JP getstart manual. With revision 594623 I modified the docs build.xml to copy the logo image to a suitable location for the ja_JP and pt_BR manuals to find. And with revision 594688 I adjusted a link to sun's web pages in the pt_BR ref manual similar to how it was changed with revision 476287 for English. Several broken links on Derby documentation web-site Key: DERBY-3030 URL: https://issues.apache.org/jira/browse/DERBY-3030 Project: Derby Issue Type: Bug Components: Build tools, Documentation, Web Site Reporter: Henri van de Scheur Assignee: Myrna van Lunteren Priority: Minor Fix For: 10.4.0.0 Attachments: Apache_Derby_LinkDoctorReport_20070905.htm, ApacheDerby_Doc_LinkDoctorReport.htm See attached htm-file for details. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: backporting changes to branches
Just some info here, maybe not everybody is aware of this, but branch 10.3 is also daily tested on 4 platforms. You will find references under http://dbtg.thresher.com/derby/test/ and details as http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.4/testing/Limited/, http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.5/testing/Limited/ and http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.6/testing/Limited/ Mike Matrigali wrote: Remember that the point of the branch is to provide a stable always working set of code that anyone can take and make either a public release of or expect that a private release will work. So only bug fixes should go in, and when I act as a committer I usually exercise more caution when backporting a fix than I might for a trunk check in. I usually first will check in a change to the trunk and then let it sit for a few days before putting it into the branch. This means that the community gets a chance to see the change, the change gets tested against a wide variety of platforms that I may not have access to (many of these test runs are available to everyone to browse from the derby website), and I usually run at least one full set of tests with the change against the branch that I am backporting to. Then after a few days I know at least in trunk no new bugs have been found across all the various platforms and go ahead with the back port if appropriate. This is just what I usually do, not the rule. It is of course up to each committer to use their experience and judgement to determine what makes sense. I still get surprised by the kinds of problems that our tests find with a change that looks straight forward to me on code review. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: code coverage for junit tests for svn 10.3 revision 579033
As far as I can see, code coverage has improved by about 8% for classes, 10% for methods, 12% for blocks, and 13% for lines since last run for svn trunk revision 529822. This is great! And thanks for running this! Ramandeep Kaur wrote: Hi, I ran code coverage for junit tests for svn 10.3 revision 579033 with sun jdk142, sun jdk15, and sun jdk16. Here are the code coverage results: OVERALL COVERAGE SUMMARY classes 89% (1167/1314) Methods 74% (15949/21667) Blocks 68% (464431/684570) Lines 68% (96187.9/141716) OVERALL STATS SUMMARY total packages: 78 total executable files: 1226 total classes: 1314 total methods: 21667 total executable lines: 141716 -- Ramandeep Kaur -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: code coverage for junit tests for svn 10.3 revision 579033
Andrew usually puts this under http://people.apache.org/~fuzzylogic/codecoverage/, but this has not been done yet for this run. Dag H. Wanvik wrote: Ramandeep Kaur [EMAIL PROTECTED] writes: Hi, I ran code coverage for junit tests for svn 10.3 revision 579033 with sun jdk142, sun jdk15, and sun jdk16. Here are the code coverage results: Are the underlying data available somewhere? Just curious to see some of that which is not covered.. Thanks, Dag OVERALL COVERAGE SUMMARY classes 89% (1167/1314) Methods 74% (15949/21667) Blocks 68% (464431/684570) Lines 68% (96187.9/141716) OVERALL STATS SUMMARY total packages: 78 total executable files: 1226 total classes: 1314 total methods: 21667 total executable lines: 141716 -- Ramandeep Kaur -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 584809 - Sun DBTG
Sorry, but the day before we had some problems checking out with svn. This went well yesterday evening, so I hope you will see a report again this evening with results as usual. [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 584809/2007-10-15 18:00:11 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-584809.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/584809_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-584809.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/584809_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-584809.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/584809_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/584809.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 580601 - Sun DBTG
About the failure in JDBCHarnessJavaTest: I double-checked the setup regarding localization and for both machines it is set up with en_us (as for all of our other machines) Myrna van Lunteren wrote: I have noticed that on vista and Win2003, in addition to the long-occurring failure with statementJdbc20 fixture of the JDBCHarnessJavaTest (which I think is related to the territory of the machine), there now is an additional failure: testTableFunctions(org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest)java.lang.NumberFormatException: For input string: 13,00 Looking at the history (http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/index_all.html), this failure first showed up in the test reports on September 13, build 575338 (http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-575338.html). Has anyone done any investigation to this issue? Regards Myrna -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Bugfixing and 10.3 maintenance release
Kathey Marsden wrote: Who would be willing to participate if I were to volunteer to be release manager for a release December 10? By participate I mean would you be willing to make fixes or test the release? I will contribute with testing the release on a number of platforms. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: [VOTE] Dyre Tjeldvoll as a committer
Rick Hillegas wrote: Please vote on whether we should make Dyre Tjeldvoll a committer. The vote will close at 5:00 pm San Francisco time on Monday September 17. +1 -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 572980S1 - Sun DBTG
We have had problems checking out from the repository. Looks like the same has happened this evening, so I am afraid tomorrows results will be the same. We will try to fix this ASAP. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 572980S1/2007-09-05 18:00:12 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-572980S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/572980S1_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-572980S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/572980S1_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-572980S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/572980S1_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/572980S1.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Updated: (DERBY-3029) Several broken links on Derby wiki-site
[ https://issues.apache.org/jira/browse/DERBY-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur updated DERBY-3029: --- Attachment: Apache_Derby_LinkDoctorReport_20070905.htm Ran the tool one more time, since DERBY-3028 was fixed, thus decreasing the number of broken links. Several broken links on Derby wiki-site --- Key: DERBY-3029 URL: https://issues.apache.org/jira/browse/DERBY-3029 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Priority: Minor Attachments: Apache_Derby_LinkDoctorReport_20070905.htm, ApacheDerby_LinkDoctorReport.htm I have used an old tool (Astra Site Manager) to check for broken links on our website and several were reported. See the htm-report, which will be attached. I have done the same check from our documentation site, but will create a separate issue for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3030) Several broken links on Derby documentation wiki-site
[ https://issues.apache.org/jira/browse/DERBY-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur updated DERBY-3030: --- Attachment: Apache_Derby_LinkDoctorReport_20070905.htm Ran the tool one more time, since DERBY-3028 was fixed, thus decreasing the number of broken links. Several broken links on Derby documentation wiki-site - Key: DERBY-3030 URL: https://issues.apache.org/jira/browse/DERBY-3030 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Priority: Minor Attachments: Apache_Derby_LinkDoctorReport_20070905.htm, ApacheDerby_Doc_LinkDoctorReport.htm See attached htm-file for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-3029) Several broken links on Derby wiki-site
Several broken links on Derby wiki-site --- Key: DERBY-3029 URL: https://issues.apache.org/jira/browse/DERBY-3029 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Priority: Minor Attachments: ApacheDerby_LinkDoctorReport.htm I have used an old tool (Astra Site Manager) to check for broken links on our website and several were reported. See the htm-report, which will be attached. I have done the same check from our documentation site, but will create a separate issue for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3029) Several broken links on Derby wiki-site
[ https://issues.apache.org/jira/browse/DERBY-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur updated DERBY-3029: --- Attachment: ApacheDerby_LinkDoctorReport.htm Several broken links on Derby wiki-site --- Key: DERBY-3029 URL: https://issues.apache.org/jira/browse/DERBY-3029 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Priority: Minor Attachments: ApacheDerby_LinkDoctorReport.htm I have used an old tool (Astra Site Manager) to check for broken links on our website and several were reported. See the htm-report, which will be attached. I have done the same check from our documentation site, but will create a separate issue for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3030) Several broken links on Derby documentation wiki-site
[ https://issues.apache.org/jira/browse/DERBY-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri van de Scheur updated DERBY-3030: --- Attachment: ApacheDerby_Doc_LinkDoctorReport.htm Several broken links on Derby documentation wiki-site - Key: DERBY-3030 URL: https://issues.apache.org/jira/browse/DERBY-3030 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Priority: Minor Attachments: ApacheDerby_Doc_LinkDoctorReport.htm See attached htm-file for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-3030) Several broken links on Derby documentation wiki-site
Several broken links on Derby documentation wiki-site - Key: DERBY-3030 URL: https://issues.apache.org/jira/browse/DERBY-3030 Project: Derby Issue Type: Bug Components: Web Site Reporter: Henri van de Scheur Priority: Minor Attachments: ApacheDerby_Doc_LinkDoctorReport.htm See attached htm-file for details. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Regression Test Report - Daily 568177 - Sun DBTG
Due to a major power outage in Trondheim, not all tests were finished on all platforms. Everything is expected to be fine again tomorrow. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 568177/2007-08-21 18:00:12 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0290290 072.17% derbyall 095039503 0 1217.18% suitesAll sles 0290290 071.66% derbyall 095039503 0 745.70% suitesAll sol 0290290 077.24% derbyall 095039503 0 1352.82% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0290290 087.26% derbyall 095039503 0 731.30% suitesAll vista 0290290 0 .% derbyall F:1,E:087838782 0 373.86% suitesAll w2003 0290290 0 .% derbyall F:1,E:087838782 0 204.87% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-568177.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/568177_bySig.html *Jvm: 1.5* lin 0289289 271.81% derbyall 078077807 0 729.27% suitesAll sles 1289288 273.50% derbyall 078077807 0 473.44% suitesAll sol 0289289 280.20% derbyall 078077807 0 718.07% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista 0289289 272.00% derbyall F:1,E:070877086 0 335.86% suitesAll w2003 0289289 275.59% derbyall F:1,E:070877086 0 222.15% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-568177.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/568177_bySig.html *Jvm: 1.4* lin 0286286 473.69% derbyall 078037803 0 665.57% suitesAll sles 0286286 471.58% derbyall NA NA NANA suitesAll sol 0286286 478.65% derbyall 078037803 0 584.67% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista 1286285 4 .% derbyall F:1,E:070837082 0 338.43% suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-568177.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/568177_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/568177.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: [VOTE] Øystein Grøvlen as a commi tter
+1 Henri Rick Hillegas wrote: Please vote on whether we should make Øystein Grøvlen a committer. The vote will close at 5:00 pm San Francisco time on Tuesday August 28.
[TESTRESULTS] Report for 10.3.1.3
Testresults for 10.3.1.3 RC3 will be published at http://dbtg.thresher.com/derby/test/ (when 'tresher' comes up) Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on 21 different OS platforms. A summary-report will be published here: http://dbtg.thresher.com/derby/test/10.3.1.3_RC/TestReport.html I have also updated http://wiki.apache.org/db-derby/TenThreePlatformTesting with these 10.3.1.3 test results. Thanks Henri
www.tresher.com unavailable
Hi! For approx. 24 hours, www.tresher.com has been unavailable. We have notified the owner of this site. We got the following answer: we're working an issue in the datacenter. I should have more information later today. Hopefully this will be fixed quite soon. Sorry for the inconvenience! Thanks! Henri
[TESTRESULTS] Report for 10.3.1.2
Testresults for 10.3.1.2 RC2 have been published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on 21 different OS platforms. A summary-report has been published here: http://dbtg.thresher.com/derby/test/10.3.1.2_RC/TestReport.html I have also updated http://wiki.apache.org/db-derby/TenThreePlatformTesting with these 10.3.1.2 test results. Thanks Henri
[jira] Created: (DERBY-2947) Reoccurrence of DERBY-861: Intermittent failure of store/readlocks.sql
Reoccurrence of DERBY-861: Intermittent failure of store/readlocks.sql --- Key: DERBY-2947 URL: https://issues.apache.org/jira/browse/DERBY-2947 Project: Derby Issue Type: Bug Components: Regression Test Failure Affects Versions: 10.3.1.2 Environment: derbyall fail * derbyall/storeall/storeall.fail:store/readlocks.sql derbyall fail * Generating report for RunSuite derbyall null null null true -- Java Information -- Java Version:1.5.0.03 Java Vendor: Hewlett-Packard Co. Java home: /opt/java1.5/jre Java classpath: /home/vo136787/hp/JavaDB-10.3.1.2/lib/derby.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyTesting.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyclient.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbynet.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbytools.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyrun.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_de_DE.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_es.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_fr.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_it.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_ja_JP.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_ko_KR.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_pt_BR.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_zh_CN.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyLocale_zh_TW.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/db2jcc.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/db2jcc_license_c.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/jakarta-oro-2.0.8.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/junit.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/jdbc2_0-stdext.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/jce1_2_2.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/geronimo-spec-jta-1.0.1B-rc4.jar:/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/geronimo-spec-servlet-2.4-rc4.jar OS name: HP-UX OS architecture: PA_RISC2.0 OS version: B.11.11 Java user name: vo136787 Java user home: /home/vo136787 Java user dir: /export/home/tmp/vo136787 java.specification.name: Java Platform API Specification java.specification.version: 1.5 - Derby Information JRE - JDBC: J2SE 5.0 - JDBC 3.0 [/tmp_mnt/home/vo136787/hp/JavaDB-10.3.1.2/lib/derby.jar] 10.3.1.2 - (556213) [/tmp_mnt/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbytools.jar] 10.3.1.2 - (556213) [/tmp_mnt/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbynet.jar] 10.3.1.2 - (556213) [/tmp_mnt/home/vo136787/hp/JavaDB-10.3.1.2/lib/derbyclient.jar] 10.3.1.2 - (556213) [/tmp_mnt/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/db2jcc.jar] 2.4 - (17) [/tmp_mnt/home/vo136787/hp/JavaDB-10.3.1.2/lib/test/db2jcc_license_c.jar] 2.4 - (17) -- - Locale Information - Current Locale : [English/United States [en_US]] Found support for locale: [cs] version: 10.3.1.2 - (556213) Found support for locale: [de_DE] version: 10.3.1.2 - (556213) Found support for locale: [es] version: 10.3.1.2 - (556213) Found support for locale: [fr] version: 10.3.1.2 - (556213) Found support for locale: [hu] version: 10.3.1.2 - (556213) Found support for locale: [it] version: 10.3.1.2 - (556213) Found support for locale: [ja_JP] version: 10.3.1.2 - (556213) Found support for locale: [ko_KR] version: 10.3.1.2 - (556213) Found support for locale: [pl] version: 10.3.1.2 - (556213) Found support for locale: [pt_BR] version: 10.3.1.2 - (556213) Found support for locale: [ru] version: 10.3.1.2 - (556213) Found support for locale: [zh_CN] version: 10.3.1.2 - (556213) Found support for locale: [zh_TW] version: 10.3.1.2 - (556213) -- Reporter: Henri van de Scheur Priority: Minor * Diff file derbyall/storeall/storemore/readlocks.diff *** Start: readlocks jdk1.5.0.03 storeall:storemore 2007-07-16 16:04:25 *** 18635a18636 APP |UserTran|ROW |1 |S |A |(4,6) |GRANT|ACTIVE 18647a18649 APP |UserTran|ROW |1 |S |A |(4,6) |GRANT|ACTIVE 18657a18660 APP |UserTran|ROW |1 |S |A |(4,6) |GRANT|ACTIVE 18666a18670 APP |UserTran|ROW |1 |S |A |(4,6) |GRANT|ACTIVE Test Failed. *** End: readlocks jdk1.5.0.03 storeall:storemore 2007-07-16 16:06:50 *** -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-2948) Reoccurrence of DERBY-2842: derbynet/testconnection.java fails with '...Connection refused: connect' expecting 'Connection refused'
/install/lib/test/db2jcc_license_c.jar] 2.4 - (17) -- - Locale Information - Current Locale : [English/United States [en_US]] Found support for locale: [cs] version: 10.3.1.2 - (556213) Found support for locale: [de_DE] version: 10.3.1.2 - (556213) Found support for locale: [es] version: 10.3.1.2 - (556213) Found support for locale: [fr] version: 10.3.1.2 - (556213) Found support for locale: [hu] version: 10.3.1.2 - (556213) Found support for locale: [it] version: 10.3.1.2 - (556213) Found support for locale: [ja_JP] version: 10.3.1.2 - (556213) Found support for locale: [ko_KR] version: 10.3.1.2 - (556213) Found support for locale: [pl] version: 10.3.1.2 - (556213) Found support for locale: [pt_BR] version: 10.3.1.2 - (556213) Found support for locale: [ru] version: 10.3.1.2 - (556213) Found support for locale: [zh_CN] version: 10.3.1.2 - (556213) Found support for locale: [zh_TW] version: 10.3.1.2 - (556213) -- Reporter: Henri van de Scheur Priority: Minor * Diff file derbyall/derbynetmats/DerbyNet/derbynetmats/testconnection.diff *** Start: testconnection jdk1.5.0_07 DerbyNet derbynetmats:derbynetmats 2007-07-16 22:17:07 *** 17d16 Could not connect to Derby Network Server on host xxxFILTERED_HOSTNAMExxx - port 9393: Connection refused ... Test Failed. *** End: testconnection jdk1.5.0_07 DerbyNet derbynetmats:derbynetmats 2007-07-16 22:20:22 *** I guess the 3 extra dots have to be included in testconnection_sed.properties ?? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-2949) AssertionFailedError in testStalePlansOnLargeTable
AssertionFailedError in testStalePlansOnLargeTable -- Key: DERBY-2949 URL: https://issues.apache.org/jira/browse/DERBY-2949 Project: Derby Issue Type: Bug Components: Regression Test Failure Affects Versions: 10.3.1.2 Environment: Microsoft© Windows VistaT Ultimate - 6.0.6000 N/A Build 6000 WindowsNT 0 6 2 X [Sun Fire X4100 Server x64 Family 15 Model 37 Stepping 1 AuthenticAMD]: ~2592 MHz, cache. 3ÿ967 Total Memory. JVM: Sun Microsystems Inc. 1.5.0_07-b03 Reporter: Henri van de Scheur Priority: Minor testStalePlansOnLargeTable(org.apache.derbyTesting.functionTests.tests.lang.StalePlansTest)junit.framework.AssertionFailedError at org.apache.derbyTesting.functionTests.tests.lang.StalePlansTest.testStalePlansOnLargeTable(StalePlansTest.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:88) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Regression Test Report - Daily 556951 - Sun DBTG
The last couple of days reports for suitesAll on Solaris x64 (sol) have shown 'UNKNOWN'. The JUnit test has crashed with: Exception in thread main java.lang.OutOfMemoryError: PermGen space Because of this there is no complete log from JUnit and the reporting scripts are unable to parse them successfully. We will have to increase the jvm's heapsize and permgen to overcome this problem. Thanks, Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 556951/2007-07-17 18:00:14 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 3298295 072.58% derbyall 084588458 0 844.34% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 3298295 078.11% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll solN+1 3298295 087.32% derbyall 084588458 0 876.47% suitesAll sparc 3298295 067.89% derbyall 084588458 0 551.80% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 3298295 0 .% derbyall F:1,E:077387737 0 157.54% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-556951.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/556951_bySig.html *Jvm: 1.5* lin 3295292 271.98% derbyall 067766776 0 503.61% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 3295292 280.60% derbyall 067766776 0 483.73% suitesAll solN+1 3295292 289.22% derbyall 067766776 0 488.98% suitesAll sparc 4295291 267.93% derbyall 067766776 0 429.14% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 3295292 275.30% derbyall F:1,E:060566055 0 171.30% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-556951.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/556951_bySig.html *Jvm: 1.4* lin 3292289 473.37% derbyall 067726772 0 462.62% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 3292289 478.84% derbyall 067726772 0 397.05% suitesAll solN+1 3292289 491.02% derbyall 067726772 0 465.23% suitesAll sparc 3292289 468.88% derbyall 067726772 0 446.19% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 3292289 4 .% derbyall F:1,E:060526051 0 .% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-556951.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/556951_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/556951.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: again, another 10.3.1. release candidate?
Hi Myrna! I understand your concern and would like to share my thoughts. I think a combination of 1) and 3) would be best. I would prefer a release now, but understand the concerns in the community and thereby the need for a new RC. After the 26th I will also start a vacation, so that would suit me fine (just in time). When we know that an update release will be started on in September, I guess that will also make it easier to accept some other critical issues in this RC. Thanks! Henri PS: I hope to post results of testing on 10.3.1.2 tomorrow. As far as I have seen so far, it looks quite good. Myrna van Lunteren wrote: Hi, There was a discussion ensuing from DERBY-2896, which I think should be a general discussion item, following mamta's check-in for a fix for that critical issue. Knut Anders Wrote: The changes in metadata.properties will not be picked up when you upgrade from 10.3.1.x to 10.3.2.x. Kathey replied: This filed as DERBY-1107 and I think is a good reason to have a new release candidate. I think other critical issues such as DERBY-2437 and the regression DERBY-2892 might be worth waiting for too if they can be fixed in short order. I wouldn't veto a release at this point but would probably vote -0. It seems to me that even though Kathey doesn't want to hold up the release, she really doesn't want a release without this fix. Which to me sounds like a new release candidate, which, as we've got a vote outstanding, means holding up the release. :-) But Kathey's email poses some options 1. I can do a fairly quick turn-around and make another release candidate after Mamta backports the fix to 10.3. If I can build the files tonight or tomorrow morning early, I can test, and call a vote around noon, that would give us until July 26th noon (PDT) and I could maybe still close the vote and hope that the maven work and web page work can be finished on that day, or leave it to Rick to do that part once he's back the week after. 2. We can wait until someone fixes DERBY-2892 for 10.3. I have not heard anything positive, nor a time frame for such a fix. If a fix happens before the 26th, I can generate new build files and open the voting, but someone else (Rick when he's back form vacation/conference?) will have to finish up the work for this release. 3. We can wait even further until other critical issues such as DERBY-2437 are fixed. I want to point out, that no has volunteered to own that one at this point, so we might be waiting indefinitely. I can, as I have suggested before, pick up the release work in September, and we can see how far the fixes are then. Or someone else can volunteer. Kathey, please be explicit, which 'other' issues except DERBY-2437 do you think are necessary to receive a fix? Myrna
[TESTRESULTS] Report for 10.3.1.1
Test results for the 10.3.1.1 RC1 will be published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on 21 different OS platforms. A summary-report wil be published here: http://dbtg.thresher.com/derby/test/10.3.1.1_RC/TestReport.html I have also updated http://wiki.apache.org/db-derby/TenThreePlatformTesting with these 10.3.1.1 test results. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: [jira] Commented: (DERBY-2918) Errors in regression tests run against 10.3.1.1 release candidate
at /export/home/rh161140/derby/dummy/testRun/system/singleUse/oneuse27 has an incompatible format with the current version of the software. The database was created by or upgraded by version 10.3. at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.init(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection30.init(Unknown Source) at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown Source) at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown Source) at org.apache.derbyTesting.junit.DataSourceConnector.openConnection(DataSourceConnector.java:54) at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:1006) at org.apache.derbyTesting.junit.BaseJDBCTestCase.openDefaultConnection(BaseJDBCTestCase.java:255) at org.apache.derbyTesting.junit.BaseJDBCTestCase.getConnection(BaseJDBCTestCase.java:92) at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.noConnectionAfterHardUpgrade(BasicSetup.java:140) ... 68 more -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: [jira] Commented: (DERBY-2918) Errors in regression tests run against 10.3.1.1 release candidate
Oops, I think you meant the other one. So far I have seen it only once: under jvm1.6 on SuSe Linux: Failure Details: * Diff file derbynetclientmats/derbynetmats/DerbyNetClient/derbynetmats/testProperties.diff *** Start: testProperties jdk1.6.0_01 DerbyNetClient derbynetmats:derbynetmats 2007-07-10 02:17:46 *** 20d19 Apache Derby Network Server - 10.3.1.1 -(EXPECTED SUBVERSION INFO) shutdown at xxFILTERED-TIMESTAMPxGMT Test Failed. *** End: testProperties jdk1.6.0_01 DerbyNetClient derbynetmats:derbynetmats 2007-07-10 02:21:06 *** Henri Henri van de Scheur wrote: If you refer to the failure in noConnectionAfterHardUpgrade, I see it under all jvm's and on all platforms. Myrna van Lunteren (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511670 ] Myrna van Lunteren commented on DERBY-2918: --- Extremely frustrating, but I don't see this! I tried the insane jars, the insane jars on my machine, the bin.zip on my machine, and downloaded the bin.zip and tried that. I'm just running the individual tests... Which distribution did you use? Who else is seeing / not seeing this? Errors in regression tests run against 10.3.1.1 release candidate - Key: DERBY-2918 URL: https://issues.apache.org/jira/browse/DERBY-2918 Project: Derby Issue Type: Bug Affects Versions: 10.3.1.1 Reporter: Rick Hillegas I am seeing errors of the following sort in metadata, odbc_metadata, NSinSameJVM, and testProperties: *** Start: metadata jdk1.4.2_12 DerbyNetClient derbynetmats:derbynetmats 2007-07-10 12:55:29 *** 16 del JDBC Driver 'Apache Derby Network Client JDBC Driver', version 10.3 (10.3.1.1 -(EXPECTED SUBVERSION INFO)) 16a16 JDBC Driver 'Apache Derby Network Client JDBC Driver', version 10.3 (10.3.1.1 - (exported)) Test Failed. *** End: metadata jdk1.4.2_12 DerbyNetClient derbynetmats:derbynetmats 2007-07-10 12:55:41 *** I am also seeing errors like the following in the JUnit upgrade tests: 1) noConnectionAfterHardUpgrade(org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup)junit.framework.ComparisonFailure: Unexpected SQL state. expected:XSLA[P] but was:XSLA[N] at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:562) at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:597) at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:611) at org.apache.derbyTesting.functionTests.tests.upgradeTests.BasicSetup.noConnectionAfterHardUpgrade(BasicSetup.java:144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:88) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57
Re: Regression Test Report - Daily 554378 - Sun DBTG
Tomorrows report will show some fewer platforms, since these machines now are used for release-testing of 10.3.1.1. Testing on the 10.2-branch has also been paused. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 554378/2007-07-08 18:00:10 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0301301 072.83% derbyall 083758375 0 714.30% suitesAll sles 0301301 072.42% derbyall 083758375 0 571.61% suitesAll sol 0301301 078.07% derbyall 083758375 0 760.59% suitesAll solN+1 0301301 085.86% derbyall 083758375 0 808.92% suitesAll sparc 0301301 068.03% derbyall 083758375 0 599.19% suitesAll vista 5300295 0 .% derbyall F:1,E:077277726 0 338.11% suitesAll w2003 2301299 0 .% derbyall F:1,E:077277726 0 157.83% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-554378.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/554378_bySig.html *Jvm: 1.5* lin 0298298 272.63% derbyall F:0,E:166936692 0 490.68% suitesAll sles 0298298 272.17% derbyall 066936693 0 342.18% suitesAll sol 0298298 281.22% derbyall 066936693 0 483.73% suitesAll solN+1 0298298 289.35% derbyall 066936693 0 486.75% suitesAll sparc 0298298 268.66% derbyall 066936693 0 431.88% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 2298296 275.84% derbyall F:1,E:060456044 0 168.30% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-554378.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/554378_bySig.html *Jvm: 1.4* lin 0295295 473.97% derbyall 066896689 0 460.00% suitesAll sles 0295295 472.05% derbyall 066896689 0 318.01% suitesAll sol 0295295 479.49% derbyall 066896689 0 406.81% suitesAll solN+1 0295295 491.26% derbyall 066896689 0 458.91% suitesAll sparc 0295295 469.27% derbyall 066896689 0 442.79% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 2295293 4 .% derbyall F:1,E:060416040 0 .% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-554378.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/554378_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/554378.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Created: (DERBY-2899) Reoccurrence of DERBY-2434: HarnessJavaTest fails on UTF-8 locale.
Reoccurrence of DERBY-2434: HarnessJavaTest fails on UTF-8 locale. -- Key: DERBY-2899 URL: https://issues.apache.org/jira/browse/DERBY-2899 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.3.1.0 Environment: Microsoft(R) Windows(R) Server 2003, - 5.2.3790 Service Pack 2 WindowsNT 2 5 Sun jvm 1.5.0_07-b03 Also seen on windows2000 and Windows Vista Reporter: Henri van de Scheur There was 1 failure: 1) statementJdbc20(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)junit.framework.ComparisonFailure: Output at line 3 expected:... parameter value '-1[,]000' for Statement.s... but was:... parameter value '-1[?]000' for Statement.s... at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:100) at org.apache.derbyTesting.functionTests.util.HarnessJavaTest.runTest(HarnessJavaTest.java:91) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:88) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) Also see logging under http://dbtg.thresher.com/derby/test/10.3.1.0_RC/jvm1.5/testing/testlog/w2003/548006-suitesAll_diff.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: re 10.3.1.0 beta platform testing DERBY-937 2434
Myrna van Lunteren wrote: Hi, For the platform testing, for Solaris Nevada, a reference was made to closed bug DERBY-937. Can someone please open a new bug with the new details? And link it to DERBY-937... See Knuts answer (thanks Knut!) Also, for Windows 2003, a reference was made to closed bug DERBY-2434. Can 2434 be reopened or the diff verified? So sorry. Thought this was only fixed on trunk and not included in 10.3. I have now created a new JIRA: DERBY-2899 Thanks a lot for following up Myrna! Henri Thx, Myrna -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: 10.3.1.1 voting testing from July 9 - July 13.
Hi Myrna! I think it was a good idea to try an earlier closing date, but I am worried for the distribution date. Would it be possible to create a new 10.3.1.1-distribution on the 5th of July? When 10.3.1.1 will be created the 9th of July, we will probably not start testing before the 10th of July, due to our different timezones. We then have less than 4 days left for testing, reporting, concluding and voting. The latter probably happening on Friday the 13th of July (urgh!... bad sign?). When your timezone then evaluates our postings, the chance is big that communication no longer is possible, because our weekend has started. I will not state the timeframe you propose is impossible - we will do our best to make it - but I think it contains a bigger risk. Thanks! Henri Myrna van Lunteren wrote: Hi, Because of vacation plans, I posted a comment to thread: http://www.nabble.com/10.3.1.0-beta-ready-for-testing-tf3937690.html#a11168181 As a result of Rick's reply, and because so far, things look fairly good, I've modified the Release Summary http://wiki.apache.org/db-derby/DerbyTenThreeRelease#head-b0d4c2f51fa87693ab17aa99eac096abbe0bd707 to show voting and sanity testing for the release candidate from July 9 - July 13. That way, should something go wrong, I can still address it, hopefully. Please let me know if this is a problem with anyone. Thx, Myrna -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: 10.3.1.0 beta ready for testing
Test results for the 10.3.1.0 Beta will be published at http://dbtg.thresher.com/derby/test/ Tests have been run with jvm1.4, jvm1.5 and jvm1.6 on 21 different OS platforms. A summary-report wil be published here: http://dbtg.thresher.com/derby/test/10.3.1.0_RC/TestReport.html I have also updated http://wiki.apache.org/db-derby/TenThreePlatformTesting with these 10.3.1.0 test results. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
[jira] Created: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.
XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO. -- Key: DERBY-2871 URL: https://issues.apache.org/jira/browse/DERBY-2871 Project: Derby Issue Type: Bug Components: JDBC Affects Versions: 10.3.1.0 Environment: OS: HP-UX v1.11 i JDK: HP 1.5.0.03 Reporter: Henri van de Scheur Priority: Minor Method: org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest Signature: %XAER_PROTO : Error executing a XAResource.commit(), server returned XAER_PROTO% Also see: http://dbtg.thresher.com/derby/test/10.3.1.0_RC/jvm1.5/testing/testlog/hpux/548006-suitesAll_diff.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: 10.3.1.0 beta ready for testing
Hi Myrna! I started testing Monday-evening, and testing itself is almost finished. Analysis and reporting will take some more time, so I am afraid I will not be able to report anything before coming Tuesday. So sorry for this. But now you at least know *your* first release is being worked on Henri Myrna van Lunteren wrote: Hi, I believe the 10.3.1.0 beta is ready for testing. You can download the (unsigned) distributions at: http://people.apache.org/~myrnavl/10.3.1.0.beta The source and doc branches are ready for use: svn co http://svn.apache.org/repos/asf/db/derby/code/branches/10.3/ svn co http://svn.apache.org/repos/asf/db/derby/docs/branches/10.3/ Please log your testing results on the following pages: http://wiki.apache.org/db-derby/TenThreePlatformTesting http://wiki.apache.org/db-derby/TenThreeBuddyTesting http://wiki.apache.org/db-derby/TenThreeApplicationTesting I'll bump the version number on the branch tomorrow. Myrna -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 548386 - Sun DBTG
2 platforms had to be taken out of the daily test to be used for 10.3.1.0-testing: SLES and Vista SolN+1 had to be rebooted. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 548386/2007-06-18 18:00:06 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0302302 072.73% derbyall 083598359 0 791.90% suitesAll sles 0302302 071.99% derbyall NA NA NANA suitesAll sol 0302302 078.21% derbyall 083598359 0 720.97% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0302302 067.93% derbyall 083598359 0 571.56% suitesAll vista 2302300 0 .% derbyall NA NA NANA suitesAll w2003 2302300 0 .% derbyall F:1,E:077117710 0 162.68% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-548386.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/548386_bySig.html *Jvm: 1.5* lin 0299299 272.16% derbyall 066796679 0 483.65% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0299299 281.33% derbyall 066796679 0 489.35% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0299299 268.79% derbyall 066796679 0 438.88% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 2299297 275.84% derbyall F:1,E:060316030 0 173.05% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-548386.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/548386_bySig.html *Jvm: 1.4* lin 0296296 473.37% derbyall 066756675 0 459.34% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0296296 479.68% derbyall 066756675 0 402.78% suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc 0296296 469.37% derbyall 066756675 0 450.33% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 2296294 4 .% derbyall F:1,E:060276026 0 .% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-548386.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/548386_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/548386.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - Daily 5????? - Sun DBTG - Buildproblems
The daily test does a new checkout. Unfortunately the same thing happened this evening. I am afraid problems are not being solved during a weekend. Thanks, Henri Jean T. Anderson wrote: Henri van de Scheur - Sun Norway wrote: Probably due to some network trouble, the daily build did not succeed and no tests are being run. Hopefully better tomorrow ERR 2007-06-16 18:06:26 Giving up checkout of https://svn.apache.org/repos/asf/db/derby/code/trunk ERR 2007-06-16 18:06:26 Checking out derby/code failed 3 attempts I never paid attention to this before. Does the daily test do a new checkout? or an 'svn up'? thanks, -jean
Regression Test Report - Daily 5????? - Sun DBTG - Buildproblems
Probably due to some network trouble, the daily build did not succeed and no tests are being run. Hopefully better tomorrow ERR 2007-06-16 18:06:26 Giving up checkout of https://svn.apache.org/repos/asf/db/derby/code/trunk ERR 2007-06-16 18:06:26 Checking out derby/code failed 3 attempts
Re: JNLP storage factory experimental modules
David Van Couvering wrote: On 6/13/07, Daniel John Debrunner [EMAIL PROTECTED] wrote: David Van Couvering wrote: +1, I agree it's just too tight for 10.3. I'd like your response to my proposal for the experimental directory; right now I'm moving forward with it (for checkin to the trunk *after* we branch for 10.3). I thought we had one already, it's called trunk. :-) OK, fair enough, but at some point in the release cycle the trunk moves from an experimental place to a place that requires stability and only features that we are comfortable supporting. It is not clear to me when or how that transformation takes place... The one thing I want to see is making our daily builds available for download so that people can play with our stuff (or is that already available and I don't know about it?) Daily builds are available though not directly from the ASF, but from groups (well at least one) who chose to them available. Anyone could do this if they so desire. Recently there was some effort at removing visibility to users of non-release builds from ASF infrastructure, to ensure that users were picking up official ASF releases. There seemed to be some confusion as to why but it did seem to be a mandate from the board. You may want to look in the archives for real details as I could be wrong (maybe infrastructure and derby-dev within the last 9 months?) Well, if the ASF doesn't want to make non-official releases available, then I believe the ASF needs to come up with an approved way of making daily or milestone builds available. Many people want to experiment with new stuff but they are not going to do it if they have to learn how to build it. I know we all know how to build Derby, but setup is not easy and we shouldn't force that on our users who want to check out our new stuff and give us feedback. What about the daily zip-files under http://dbtg.thresher.com/derby/bits/trunk/ ? David Dan.
Re: Regression Test Report - Daily 545761 - Sun DBTG
We didn't make it within the planned time frame. Some platforms are being tested partially, some others not at all. But tonight everything will run as before, including the runs on the 10.2-branch. Henri Henri van de Scheur wrote: Some environmental issue in our testinfrastructure, caused problems for our testing. This will be solved today, meaning that testing will be back to normal from this evening and all results will be reported the usual way tomorrow. Sorry for the inconvenience this might cause! Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 545761/2007-06-09 18:00:10 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0305305 073.22% derbyall 081628162 0 707.09% suitesAll sles 0305305 072.68% derbyall 081628162 0 416.04% suitesAll sol 0305305 077.88% derbyall 081628162 0 744.19% suitesAll solN+1 0305305 085.71% derbyall 081628162 0 705.25% suitesAll sparc 0305305 068.54% derbyall 081628162 0 557.95% suitesAll vista 0305305 0 .% derbyall F:2,E:076437641 0 259.19% suitesAll w2003 0305305 0 .% derbyall F:2,E:076437641 0 150.69% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-545761.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/545761_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista 1302301 272.42% derbyall F:3,E:059775974 0 235.40% suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-545761.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/545761_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-545761.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/545761_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/545761.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 545761 - Sun DBTG
Some environmental issue in our testinfrastructure, caused problems for our testing. This will be solved today, meaning that testing will be back to normal from this evening and all results will be reported the usual way tomorrow. Sorry for the inconvenience this might cause! Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 545761/2007-06-09 18:00:10 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0305305 073.22% derbyall 081628162 0 707.09% suitesAll sles 0305305 072.68% derbyall 081628162 0 416.04% suitesAll sol 0305305 077.88% derbyall 081628162 0 744.19% suitesAll solN+1 0305305 085.71% derbyall 081628162 0 705.25% suitesAll sparc 0305305 068.54% derbyall 081628162 0 557.95% suitesAll vista 0305305 0 .% derbyall F:2,E:076437641 0 259.19% suitesAll w2003 0305305 0 .% derbyall F:2,E:076437641 0 150.69% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-545761.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/545761_bySig.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista 1302301 272.42% derbyall F:3,E:059775974 0 235.40% suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-545761.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/545761_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-545761.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/545761_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/545761.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 539889 - Sun DBTG
I forgot to mention that machines for sles and vista are temporarily in use for other purposes, so they will not show any results. This also applies for all testing on the 10.2-branch. I hope to restart this again in 1 or 2 days. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 539889/2007-05-20 18:00:12 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0313313 074.18% derbyall F:69,E:3081538054 0 716.29% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0313313 078.98% derbyall F:69,E:3081538054 0 680.93% suitesAll solN+1 0313313 087.05% derbyall F:69,E:3081538054 0 810.92% suitesAll sparc 0313313 069.34% derbyall F:69,E:3081538054 0 460.46% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 0313313 0 .% derbyall F:70,E:3181538052 0 194.57% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-539889.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/539889.html *Jvm: 1.5* lin 0306306 273.46% derbyall F:69,E:3065086409 0 508.55% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0306306 281.64% derbyall F:69,E:3065086409 0 441.76% suitesAll solN+1 0306306 290.27% derbyall F:69,E:3065086409 0 443.37% suitesAll sparc 0306306 269.65% derbyall F:69,E:3065086409 0 379.91% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 0306306 276.51% derbyall F:70,E:3065086408 0 173.56% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-539889.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/539889.html *Jvm: 1.4* lin 0303303 474.74% derbyall F:69,E:3065046405 0 466.22% suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol 0303303 480.32% derbyall F:69,E:3065046405 0 357.58% suitesAll solN+1 0303303 491.40% derbyall F:69,E:3065046405 0 417.19% suitesAll sparc 0303303 470.44% derbyall F:69,E:3065046405 0 390.06% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 0303303 4 .% derbyall F:71,E:3065046403 0 .% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-539889.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/539889.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/539889.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 529300 - Sun DBTG
I am sorry, our build was broken and I discovered it too late to restart. Today everything is back to normal again. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 529300/2007-04-16 18:00:14 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-529300.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/529300.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-529300.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/529300.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-529300.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/529300.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/529300.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 524622S5 - Sun DBTG
For several days now, reporting of our testing has had some failures resulting in erroneous reports. My apologies for the inconvenience. I hope to fix this tomorrow when I am back from a short Easter-vacation. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 524622S5/2007-04-01 18:00:12 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-524622S5.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/524622S5.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-524622S5.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/524622S5.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-524622S5.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/524622S5.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/524622S5.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - Daily 522555S1 - Sun DBTG
Due to local network-problems, our svn-update failed and build was broken. No tests were run. The situation is back to normal and tests are running.. [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 522555S1/2007-03-26 18:00:10 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-522555S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/522555S1.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-522555S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/522555S1.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-522555S1.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/522555S1.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/522555S1.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 522289 - Sun DBTG
No tests were run due to a build-break which was also reported by the Tinderbox-build. [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 522289/2007-03-25 18:00:11 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-522289.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/522289.html *Jvm: 1.5* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-522289.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/522289.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-522289.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/522289.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/522289.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: [VOTE] Dag Wanvik as a committer
+1 Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
Re: Regression Test Report - Daily 514731 - Sun DBTG
The report send here, was from the day before. Something went wrong in our daily building resulting in no tests run. Todays build-procedure seems to be fine, so tomorrow test-results will be posted as usual. Henri [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 514731/2007-03-05 18:00:12 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 1425424 089.64% derbyall 068756875 0 376.60% suitesAll sles 0425425 093.58% derbyall 068756875 0 211.58% suitesAll sol 0425425 094.29% derbyall 068756875 0 443.13% suitesAll solN+1 0425425 0 113.91% derbyall 068756875 0 369.95% suitesAll sparc 0425425 098.78% derbyall 068756875 0 259.62% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-514731.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/514731.html *Jvm: 1.5* lin 0420420 288.93% derbyall 052495249 0 284.22% suitesAll sles 1420419 292.78% derbyall 052495249 0 172.82% suitesAll sol 0420420 297.82% derbyall 052495249 0 235.14% suitesAll solN+1 0420420 2 118.42% derbyall 052495249 0 243.93% suitesAll sparc 0420420 298.52% derbyall 052495249 0 220.51% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll win 0420420 2 108.05% derbyall F:3,E:052495246 0 160.05% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-514731.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/514731.html *Jvm: 1.4* lin 0415415 489.89% derbyall 052455245 0 267.70% suitesAll sles 0415415 492.99% derbyall 052455245 0 168.19% suitesAll sol 0415415 495.30% derbyall 052455245 0 207.27% suitesAll solN+1 0415415 4 120.56% derbyall 052455245 0 240.07% suitesAll sparc 0415415 499.99% derbyall 052455245 0 244.86% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll win 0415415 462.22% derbyall F:1,E:052455244 0 162.37% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-514731.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/514731.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/514731.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: Regression Test Report - Daily 509253 - Sun DBTG
For this report we still had some problems running under jvm1.4. We have now increased jvm max memory to 256M and that seems to help [EMAIL PROTECTED] wrote: [Auto-generated mail] *Daily* 509253/2007-02-19 18:00:11 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 1431430 090.83% derbyall F:1,E:068016800 0 324.72% suitesAll sles 2431429 097.62% derbyall F:1,E:068016800 0 197.39% suitesAll sol 0431431 095.36% derbyall F:1,E:068016800 0 334.18% suitesAll solN+1 0431431 0 114.70% derbyall F:1,E:068016800 0 311.34% suitesAll sparc 0431431 098.78% derbyall F:1,E:068016800 0 209.17% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-509253.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/509253.html *Jvm: 1.5* lin 0427427 290.07% derbyall F:1,E:025412540 0 256.84% suitesAll sles 0427427 295.29% derbyall F:1,E:025412540 0 159.55% suitesAll sol 0427427 298.96% derbyall F:1,E:025412540 0 212.04% suitesAll solN+1 0427427 2 119.12% derbyall F:1,E:025412540 0 221.61% suitesAll sparc 0427427 299.44% derbyall F:1,E:025412540 0 209.40% suitesAll vista 0427427 294.41% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll win 0427427 2 109.93% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-509253.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/509253.html *Jvm: 1.4* lin 0421421 491.20% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll sles 0421421 495.77% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll sol 0421421 496.37% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll solN+1 0421421 4 120.76% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll sparc 0421421 4 100.51% derbyall UNKOWNUNKOWNUNKOWN UNKOWN 0.00% suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll win NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-509253.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/509253.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/509253.txt ( All results in http://dbtg.thresher.com/derby/test/ ) -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway
