[jira] Created: (DERBY-4540) 'AssertionFailedError' in 'store.AccessTest.testCS4595B_UniqueIndex(AccessTest.java:1729)' on SUSE Linux / IBM JIT - r9

'AssertionFailedError' in 'store.AccessTest.testCS4595B_UniqueIndex(AccessTest.java:1729)' on SUSE Linux / IBM JIT - r9 Key: DERBY-4540

[jira] Commented: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796115#action_12796115 ] Ole Solberg commented on DERBY-4417: Committed DERBY-4417_P2_p1.diff.txt to trunk as

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Issue fix info: (was: [Patch Available]) Enable distributed replication testing - master server,

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Attachment: DERBY-4417_P1_p1.diff DERBY-4417_P1_p1.diff.txt: -- This patch

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Issue fix info: [Patch Available] DERBY-4417_P1_p1.diff.txt intended for commit. Enable

[jira] Commented: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12795304#action_12795304 ] Ole Solberg commented on DERBY-4417: Committed DERBY-4417_P1_p1.diff to trunk as

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Issue fix info: (was: [Patch Available]) Enable distributed replication testing - master server,

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Attachment: DERBY-4417_P2_p1.diff.txt DERBY-4417_P2_p1.diff.txt: --- This

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Issue fix info: [Patch Available] Enable distributed replication testing - master server, slave

[jira] Commented: (DERBY-4461) 'testD151(...Derby151Test)java.sql.SQLException: Failed to start database' (and more ...) on Suse EE S 10 Linux/IBM 1.6.0, Fedora Core 5/Sun 1.6.0-b105, Win XP/Sun 1.6.0

[ https://issues.apache.org/jira/browse/DERBY-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788720#action_12788720 ] Ole Solberg commented on DERBY-4461: I see a variant(?) of this in last nights

[jira] Commented: (DERBY-4297) 'compilation time did not compute (0,0,0,0) expected:16 but was:0' in testGroupBySortProps(....tests.lang.XplainStatisticsTest)

[ https://issues.apache.org/jira/browse/DERBY-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12785813#action_12785813 ] Ole Solberg commented on DERBY-4297: Hi Brian, I see 9 occurences of this signature

[jira] Created: (DERBY-4461) 'testD151(...Derby151Test)java.sql.SQLException: Failed to start database' (and more ...) on Suse EE S 10 Linux/IBM 1.6.0, Fedora Core 5/Sun 1.6.0-b105, Win XP/Sun 1.6.0_1

'testD151(...Derby151Test)java.sql.SQLException: Failed to start database' (and more ...) on Suse EE S 10 Linux/IBM 1.6.0, Fedora Core 5/Sun 1.6.0-b105, Win XP/Sun 1.6.0_10

[jira] Closed: (DERBY-4457) 'Column value mismatch' in 'testDistinctInsertWithGeneratedColumn(...lang.DistinctTest)' on Jvm 1.5, 1.4, phoneME.

[ https://issues.apache.org/jira/browse/DERBY-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4457. -- 'Column value mismatch' in 'testDistinctInsertWithGeneratedColumn(...lang.DistinctTest)' on Jvm 1.5,

[jira] Created: (DERBY-4457) 'Column value mismatch' in 'testDistinctInsertWithGeneratedColumn(...lang.DistinctTest)' on Jvm 1.5, 1.6, phoneME.

'Column value mismatch' in 'testDistinctInsertWithGeneratedColumn(...lang.DistinctTest)' on Jvm 1.5, 1.6, phoneME. -- Key: DERBY-4457 URL:

[jira] Updated: (DERBY-4457) 'Column value mismatch' in 'testDistinctInsertWithGeneratedColumn(...lang.DistinctTest)' on Jvm 1.5, 1.4, phoneME.

[ https://issues.apache.org/jira/browse/DERBY-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4457: --- Summary: 'Column value mismatch' in 'testDistinctInsertWithGeneratedColumn(...lang.DistinctTest)' on

[jira] Closed: (DERBY-4454) ...lang.UDTTest fails on phoneME w/ An attempt was made to get a data value of type 'java.lang.Object' from a data value of type 'DECIMAL'

[ https://issues.apache.org/jira/browse/DERBY-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4454. -- ...lang.UDTTest fails on phoneME w/ An attempt was made to get a data value of type 'java.lang.Object'

[jira] Created: (DERBY-4454) ...lang.UDTTest fails on phoneME w/ An attempt was made to get a data value of type 'java.lang.Object' from a data value of type 'DECIMAL'

...lang.UDTTest fails on phoneME w/ An attempt was made to get a data value of type 'java.lang.Object' from a data value of type 'DECIMAL'

[jira] Commented: (DERBY-4453) OnlineBackupTest1 nightly test failed with java.io.EOFException: Reached end of file while attempting to read a whole page.

[ https://issues.apache.org/jira/browse/DERBY-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12782339#action_12782339 ] Ole Solberg commented on DERBY-4453: The test directory has been cleaned. But if there

[jira] Commented: (DERBY-4453) OnlineBackupTest1 nightly test failed with java.io.EOFException: Reached end of file while attempting to read a whole page.

[ https://issues.apache.org/jira/browse/DERBY-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781814#action_12781814 ] Ole Solberg commented on DERBY-4453: The complete log from the test is now available as

[jira] Closed: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4429. -- Resolution: Fixed Let StressMultiTest read Threads and Minutes to run as system property

[jira] Closed: (DERBY-4438) 'Table/View 'T1' already exists in Schema 'APP'' in lang.DropTableTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4438. -- 'Table/View 'T1' already exists in Schema 'APP'' in lang.DropTableTest on phoneME/cvm

[jira] Updated: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4429: --- Issue fix info: [Patch Available] Let StressMultiTest read Threads and Minutes to run as system

[jira] Commented: (DERBY-4290) suites.All hangs on phoneME/cvm - caused by cvm/phoneME error

[ https://issues.apache.org/jira/browse/DERBY-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772955#action_12772955 ] Ole Solberg commented on DERBY-4290: 790489 backported to 10.5 with revision 832349.

[jira] Updated: (DERBY-4290) suites.All hangs on phoneME/cvm - caused by cvm/phoneME error

[ https://issues.apache.org/jira/browse/DERBY-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4290: --- Affects Version/s: 10.5.3.1 suites.All hangs on phoneME/cvm - caused by cvm/phoneME error

[jira] Closed: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4427. -- Resolution: Fixed TestConfiguration.existingServerSuite(,portNumber) must use the supplied

[jira] Updated: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4427: --- Affects Version/s: (was: 10.5.3.0) The problem was not in 10.5. 10.5 had the original correct

[jira] Commented: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772979#action_12772979 ] Ole Solberg commented on DERBY-4429: Committed DERBY-StressMultiOptions_diff_2 to trunk

[jira] Updated: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4429: --- Issue fix info: (was: [Patch Available]) Let StressMultiTest read Threads and Minutes to run as

[jira] Created: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

Let StressMultiTest read Threads and Minutes to run as system property -- Key: DERBY-4429 URL: https://issues.apache.org/jira/browse/DERBY-4429 Project: Derby Issue Type:

[jira] Updated: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4429: --- Attachment: DERBY-StressMultiOptions_stat.txt DERBY-StressMultiOptions_diff.txt Let

[jira] Commented: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12772531#action_12772531 ] Ole Solberg commented on DERBY-4429: Thanks for catching that Kristian! It should be

[jira] Updated: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4429: --- Description: Allow StressMultiTest to read System Property derby.tests.ThreadsMinutes to set

[jira] Updated: (DERBY-4429) Let StressMultiTest read Threads and Minutes to run as system property

[ https://issues.apache.org/jira/browse/DERBY-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4429: --- Attachment: DERBY-StressMultiOptions_stat_2.txt DERBY-StressMultiOptions_diff_2.txt

[jira] Updated: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4427: --- Component/s: (was: Replication) TestConfiguration.existingServerSuite(,portNumber) must use

[jira] Commented: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771386#action_12771386 ] Ole Solberg commented on DERBY-4427: Yes, for completeness, it should be backported.

[jira] Commented: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12771388#action_12771388 ] Ole Solberg commented on DERBY-4427: Committed DERBY-existingServer_Fix_stat.txt to

[jira] Updated: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4427: --- Issue fix info: (was: [Patch Available]) Affects Version/s: 10.5.3.0

[jira] Created: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

TestConfiguration.existingServerSuite(,portNumber) must use the supplied portNumber --- Key: DERBY-4427 URL: https://issues.apache.org/jira/browse/DERBY-4427

[jira] Updated: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4427: --- Issue fix info: [Patch Available] TestConfiguration.existingServerSuite(,portNumber) must use

[jira] Updated: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

[ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4427: --- Attachment: DERBY-existingServer_Fix_stat.txt DERBY-existingServer_Fix_diff.txt

[jira] Commented: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12769113#action_12769113 ] Ole Solberg commented on DERBY-4417: Thanks, Dag! I will fix these in the next upload

[jira] Created: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

Enable distributed replication testing - master server, slave server and test client running on different hosts. Key: DERBY-4417 URL:

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Attachment: DERBY_distr_repl_C-replicationtest.properties DERBY_distr_repl_B.diff.txt

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Attachment: DERBY_distr_repl_D-start_script.txt Enable distributed replication testing - master

[jira] Updated: (DERBY-4417) Enable distributed replication testing - master server, slave server and test client running on different hosts.

[ https://issues.apache.org/jira/browse/DERBY-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4417: --- Component/s: Test Replication Affects Version/s: 10.6.0.0 Enable

[jira] Created: (DERBY-4418) derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15 on Solaris

derbyall/encryptionAll/encryptionAll/aes fails on 10.4, 10.3 and 10.2 with Sun JVM 1.6.0_15 on Solaris -- Key: DERBY-4418 URL:

[jira] Commented: (DERBY-4409) Make some tests run faster by using CleanDatabaseSetup + decorateSQL + rollback idiom

[ https://issues.apache.org/jira/browse/DERBY-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12766501#action_12766501 ] Ole Solberg commented on DERBY-4409: TinderBox test / suites.All failed with just

[jira] Updated: (DERBY-4409) Make some tests run faster by using CleanDatabaseSetup + decorateSQL + rollback idiom

[ https://issues.apache.org/jira/browse/DERBY-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4409: --- Attachment: DERBY-4409_min_stat.txt DERBY-4409_min_diff.txt DERBY-4409_min_diff.txt:

[jira] Commented: (DERBY-4409) Make some tests run faster by using CleanDatabaseSetup + decorateSQL + rollback idiom

[ https://issues.apache.org/jira/browse/DERBY-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12766506#action_12766506 ] Ole Solberg commented on DERBY-4409: DERBY-4409_min_diff.txt committed to trunk as

[jira] Closed: (DERBY-4188) XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID' is not a column in table or VTI 'XPLTEST.SYSXPLAIN_RESULTSETS'.' was thrown while evaluating

[ https://issues.apache.org/jira/browse/DERBY-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4188. -- XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID' is not a column in table

[jira] Closed: (DERBY-3824) Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints: T1 row count: expected:1 but was:8

[ https://issues.apache.org/jira/browse/DERBY-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-3824. -- Resolution: Fixed Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints:

[jira] Closed: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-3925. -- Resolution: Fixed testMetaDataQueryRunInSYScompilationSchema(.upgradeTests.Changes10_4) fails

[jira] Assigned: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg reassigned DERBY-3925: -- Assignee: Ole Solberg

[jira] Updated: (DERBY-3824) Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints: T1 row count: expected:1 but was:8

[ https://issues.apache.org/jira/browse/DERBY-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3824: --- Issue fix info: [Patch Available] Rollback to savepoint fails on phoneME -

[jira] Updated: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3925: --- Attachment: DERBY-3925_1.diff.txt DERBY-3925_1.diff.txt changes

[jira] Updated: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3925: --- Issue fix info: [Patch Available]

[jira] Commented: (DERBY-3824) Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints: T1 row count: expected:1 but was:8

[ https://issues.apache.org/jira/browse/DERBY-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12763980#action_12763980 ] Ole Solberg commented on DERBY-3824: Committed DERBY-3824_1.diff.txt to trunk as rev.

[jira] Updated: (DERBY-3824) Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints: T1 row count: expected:1 but was:8

[ https://issues.apache.org/jira/browse/DERBY-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3824: --- Issue fix info: (was: [Patch Available]) Rollback to savepoint fails on phoneME -

[jira] Updated: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3925: --- Attachment: DERBY-3925_2.diff.txt Thanks Knut, for reviewing! Added the break out of the loop.

[jira] Updated: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3925: --- Issue fix info: (was: [Patch Available])

[jira] Commented: (DERBY-3925) testMetaDataQueryRunInSYScompilationSchema(.....upgradeTests.Changes10_4) fails on CVM/phoneME

[ https://issues.apache.org/jira/browse/DERBY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12764029#action_12764029 ] Ole Solberg commented on DERBY-3925: Committed DERBY-3925_2.diff.txt to trunk as rev.

[jira] Closed: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4393. -- lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[jira] Resolved: (DERBY-4188) XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID' is not a column in table or VTI 'XPLTEST.SYSXPLAIN_RESULTSETS'.' was thrown while evaluatin

[ https://issues.apache.org/jira/browse/DERBY-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg resolved DERBY-4188. Resolution: Fixed XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID'

[jira] Commented: (DERBY-4188) XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID' is not a column in table or VTI 'XPLTEST.SYSXPLAIN_RESULTSETS'.' was thrown while evaluati

[ https://issues.apache.org/jira/browse/DERBY-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12763381#action_12763381 ] Ole Solberg commented on DERBY-4188: DERBY-4188_1.diff.txt committed to trunk as

[jira] Assigned: (DERBY-4188) XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID' is not a column in table or VTI 'XPLTEST.SYSXPLAIN_RESULTSETS'.' was thrown while evaluatin

[ https://issues.apache.org/jira/browse/DERBY-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg reassigned DERBY-4188: -- Assignee: Ole Solberg XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException:

[jira] Assigned: (DERBY-3824) Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints: T1 row count: expected:1 but was:8

[ https://issues.apache.org/jira/browse/DERBY-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg reassigned DERBY-3824: -- Assignee: Ole Solberg Rollback to savepoint fails on phoneME -

[jira] Updated: (DERBY-3824) Rollback to savepoint fails on phoneME - xtestRollbackWillReleaseLaterSavepoints: T1 row count: expected:1 but was:8

[ https://issues.apache.org/jira/browse/DERBY-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3824: --- Attachment: DERBY-3824_1.diff.txt DERBY-3824_1.diff.txt: Some testcases in SavepointJdbc30Test did

[jira] Resolved: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg resolved DERBY-4393. Resolution: Fixed lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on

[jira] Closed: (DERBY-4392) Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4392. -- Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

[jira] Resolved: (DERBY-4392) Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg resolved DERBY-4392. Resolution: Fixed Table/View / Constraint already exists in Schema 'APP' in

[jira] Commented: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762986#action_12762986 ] Ole Solberg commented on DERBY-4393: DERBY-4393_4.diff.txt committed to trunk as

[jira] Updated: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4393: --- Issue fix info: (was: [Patch Available]) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already

[jira] Updated: (DERBY-4188) XplainStatisticsTest fails w/ 'The exception 'java.sql.SQLException: 'RS_ID' is not a column in table or VTI 'XPLTEST.SYSXPLAIN_RESULTSETS'.' was thrown while evaluating

[ https://issues.apache.org/jira/browse/DERBY-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4188: --- Attachment: DERBY-4188_1.diff.txt Some testcases in XplainStatisticsTest did not take into account

[jira] Updated: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4393: --- Attachment: DERBY-4393_4.diff.txt DERBY-4393_4.diff.txt replaces DERBY-4393_3.diff.txt. Still has

[jira] Commented: (DERBY-4392) Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12762110#action_12762110 ] Ole Solberg commented on DERBY-4392: DERBY-4392_1.diff.txt was committed to trunk with

[jira] Assigned: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg reassigned DERBY-4393: -- Assignee: Ole Solberg lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on

[jira] Updated: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4393: --- Issue fix info: [Patch Available] lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists.

[jira] Updated: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4393: --- Attachment: DERBY-4393_1.diff.txt Partial patch. Cleanup (drop) for CREATE SEQUENCE alpha_seq. Does

[jira] Updated: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4393: --- Attachment: DERBY-4393_2.diff.txt DERBY-4393_2.diff.txt replaces DERBY-4393_1.diff.txt: adding

[jira] Updated: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4393: --- Attachment: DERBY-4393_3.diff.txt DERBY-4393_3.diff.txt replaces DERBY-4393_2.diff.txt. This patch

[jira] Assigned: (DERBY-4392) Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg reassigned DERBY-4392: -- Assignee: Ole Solberg Table/View / Constraint already exists in Schema 'APP' in

[jira] Updated: (DERBY-4392) Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4392: --- Attachment: DERBY-4392_1.diff.txt CheckConstraintTest.testBuiltInFunctions() should do clean up:

[jira] Created: (DERBY-4392) Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm

Table/View / Constraint already exists in Schema 'APP' in lang.CheckConstraintTest on phoneME/cvm --- Key: DERBY-4392 URL:

[jira] Created: (DERBY-4393) lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm

lang.SequenceTest fails w/ Sequence 'ALPHA_SEQ' already exists. on phoneME/cvm Key: DERBY-4393 URL: https://issues.apache.org/jira/browse/DERBY-4393 Project: Derby

[jira] Closed: (DERBY-4359) Make UpgradeTrajectoryTest run on JVM 1.6

[ https://issues.apache.org/jira/browse/DERBY-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4359. -- Make UpgradeTrajectoryTest run on JVM 1.6 -

[jira] Commented: (DERBY-4361) testDefault fixture in engine.ErrorStreamTest has been failing with junit.framework.AssertionFailedError: File C:\jartest\JarResults.XXdateXX\ibm15_suites.All\system\der

[ https://issues.apache.org/jira/browse/DERBY-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12748300#action_12748300 ] Ole Solberg commented on DERBY-4361: Also seen in the Sun testing:

[jira] Created: (DERBY-4358) Improvements to UpgradeTrajectoryTest

Improvements to UpgradeTrajectoryTest - Key: DERBY-4358 URL: https://issues.apache.org/jira/browse/DERBY-4358 Project: Derby Issue Type: Task Components: Test Affects Versions: 10.6.0.0

[jira] Created: (DERBY-4359) Make UpgradeTrajectoryTest run on JVM 1.6

Make UpgradeTrajectoryTest run on JVM 1.6 - Key: DERBY-4359 URL: https://issues.apache.org/jira/browse/DERBY-4359 Project: Derby Issue Type: Improvement Components: Test Affects

[jira] Created: (DERBY-4360) Avoid memory exhaustion when running UpgradeTrajectoryTest w/-DderbyTesting.allTrajectories=true

Avoid memory exhaustion when running UpgradeTrajectoryTest w/-DderbyTesting.allTrajectories=true Key: DERBY-4360 URL:

[jira] Updated: (DERBY-4359) Make UpgradeTrajectoryTest run on JVM 1.6

[ https://issues.apache.org/jira/browse/DERBY-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4359: --- Issue Type: Sub-task (was: Improvement) Parent: DERBY-4358 Make UpgradeTrajectoryTest run

[jira] Updated: (DERBY-4360) Avoid memory exhaustion when running UpgradeTrajectoryTest w/-DderbyTesting.allTrajectories=true

[ https://issues.apache.org/jira/browse/DERBY-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4360: --- Issue Type: Sub-task (was: Improvement) Parent: DERBY-4358 Avoid memory exhaustion when

[jira] Created: (DERBY-4356) testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:2 but wa

testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:2 but was:%

[jira] Updated: (DERBY-4356) testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:2 but wa

[ https://issues.apache.org/jira/browse/DERBY-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-4356: --- Affects Version/s: 10.4.3.0

[jira] Commented: (DERBY-4356) testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:2 but

[ https://issues.apache.org/jira/browse/DERBY-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744963#action_12744963 ] Ole Solberg commented on DERBY-4356: On Windows platforms we also see

[jira] Closed: (DERBY-4246) '.replicationTests.ReplicationRun_Local_3_p5).testReplication_Local_3_p5_DERBY_3878()' fails w/ Could not perform operation 'stopSlave' because the database '...' has not

[ https://issues.apache.org/jira/browse/DERBY-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4246. -- Not seen since commit, so closing.

[jira] Closed: (DERBY-3719) '...replication.buffer.LogBufferFullException' causes failover to fail w/ 'XRE07, SQLERRMC: Could not perform operation because the database is not in replication master mo

[ https://issues.apache.org/jira/browse/DERBY-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-3719. -- Not seen since commit, so closing. '...replication.buffer.LogBufferFullException' causes failover to

[jira] Closed: (DERBY-3296) Importing to table in default schema fails when another table with the same name exists in a different schema

[ https://issues.apache.org/jira/browse/DERBY-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-3296. -- Bug behavior facts: [Regression Test Failure] Not seen since commit, so closing. Importing to table

[jira] Closed: (DERBY-4290) suites.All hangs on phoneME/cvm - caused by cvm/phoneME error

[ https://issues.apache.org/jira/browse/DERBY-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-4290. -- Resolution: Fixed suites.All hangs on phoneME/cvm - caused by cvm/phoneME error

[jira] Closed: (DERBY-3921) Replication: Test replication of encrypted databases

[ https://issues.apache.org/jira/browse/DERBY-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-3921. -- Resolution: Fixed Replication: Test replication of encrypted databases

[jira] Created: (DERBY-4297) 'compilation time did not compute (0,0,0,0) expected:16 but was:0' in testGroupBySortProps(....tests.lang.XplainStatisticsTest)

'compilation time did not compute (0,0,0,0) expected:16 but was:0' in testGroupBySortProps(tests.lang.XplainStatisticsTest) --- Key: DERBY-4297

  1   2   3   4   5   6   7   >