You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2011/06/20 21:50:47 UTC
[jira] [Created] (DERBY-5288) running multiple suites.All
concurrently should be possible
running multiple suites.All concurrently should be possible
-----------------------------------------------------------
Key: DERBY-5288
URL: https://issues.apache.org/jira/browse/DERBY-5288
Project: Derby
Issue Type: Bug
Components: Test
Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.4, 10.9.0.0
Reporter: Myrna van Lunteren
Assignee: Myrna van Lunteren
When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
-Dderby.tests.basePort, there are still a few tests that fail regularly.
The first one is SecureServerTest.
See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056642#comment-13056642 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
After my check-ins to 10.6 and 10.7 the weme 6.2 runs didn't complete. I'll investigate.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren closed DERBY-5288.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.8.2.2
10.9.0.0
I've verified this works with 10.8 and trunk (10.9 alpha). I've not tried this with earlier versions, but I think it should be possible with 10.7.
Closing this issue.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.2.2, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Fix For: 10.9.0.0, 10.8.2.2
>
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054166#comment-13054166 ]
Knut Anders Hatlen commented on DERBY-5288:
-------------------------------------------
FWIW, I've never been able to run suites.All on jdk16 with default memory settings without getting the PermGen space error you saw, even when not running concurrent tests (default PermGen size is 64MB, I run with 256MB).
Another thing to take into consideration is that some of the tests fork a new JVM for the network server, so you may get into the situation where your 8 test runs have 16 processes running at the same time (if all happen to be in such a test at the same time). Then you'd only have ~240 MB per process, which in my experience is too little for suites.All. When I run concurrent tests, I typically split up suites.All in smaller test suites (jdbcapi._Suite, lang._Suite, etc...) and run them individually so that each process doesn't grow too big.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052969#comment-13052969 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
committed to trunk with revision 1138201.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.4, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054198#comment-13054198 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
I double-checked my testresults, and I was incorrect. I had run SecureServerTest with my previous change & with the latest change, with trunk & 4 jvms (each twice), but the other experiment was to backport the change of 1138201 manually to 10.6, 10.7, and 10.8, and then I ran with ibm 1.5 and ibm 1.6 for each of the 4 branches. With ibm 1.5 and 1.6 I did not run out of memory, so that explains that.
I'll backport the current change.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054034#comment-13054034 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
Thanks for the commit.
Unfortunately, when I ran suites.All on my windowsXP with this change, with 8 concurrent jvms (4 different ones, ibm142, ibm15, ibm16 and jdk16) 4 of them, the ibm142 and jdk16 ones, ran OutOfMemory with messages like this:
jdk16:
Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
--------------------------------------
ibm 142:
SetQueryTimeoutTest java.lang.OutOfMemoryError: JVMCI015:OutOfMemoryError, cannot create anymore threads due to memory or resource constraints
at java.lang.Thread.start(Native Method)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.SetQueryTimeoutTest.testTimeoutWithExec(SetQueryTimeoutTest.java:538)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.SetQueryTimeoutTest.go(SetQueryTimeoutTest.java:753)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.SetQueryTimeoutTest.main(SetQueryTimeoutTest.java:722)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at org.apache.derbyTesting.functionTests.util.HarnessJavaTest.runTest(HarnessJavaTest.java:87)
at junit.framework.TestCase.runBare(TestCase.java(Compiled Code))
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java(Compiled Code))
at junit.framework.TestResult$1.protect(TestResult.java(Inlined Compiled Code))
at junit.framework.TestResult.runProtected(TestResult.java(Inlined Compiled Code))
at junit.framework.TestResult.run(TestResult.java(Inlined Compiled Code))
at junit.framework.TestCase.run(TestCase.java(Compiled Code))
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java(Compiled Code))
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java(Compiled Code))
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java(Compiled Code))
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.framework.TestSuite.runTest(TestSuite.java(Inlined Compiled Code))
at junit.framework.TestSuite.run(TestSuite.java(Compiled Code))
at junit.framework.TestSuite.runTest(TestSuite.java(Inlined Compiled Code))
at junit.framework.TestSuite.run(TestSuite.java(Compiled Code))
at junit.framework.TestSuite.runTest(TestSuite.java(Inlined Compiled Code))
at junit.framework.TestSuite.run(TestSuite.java(Compiled Code))
at junit.framework.TestSuite.runTest(TestSuite.java(Compiled Code))
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.textui.TestRunner.doRun(TestRunner.java:116)
at junit.textui.TestRunner.start(TestRunner.java:172)
at junit.textui.TestRunner.main(TestRunner.java:138)
--------------------------------------
The ibm 1.4.2 processes hung after this. The jdk16 processes have exited.
Any further help on this will be very welcome...
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-5288:
--------------------------------------
Attachment: DERBY-5288_1.diff
Attaching a patch which removes the setting of the thread to MIN_PRIORITY and adds the join on the streamReader thread with a time-out (otherwise there's a chance of hanging tests).
If there are no comments on this I intend to commit this and backport it to 10.8, 10.7, and 10.6, as those are the branches I think support running the junit tests concurrently.
With this change backported I did run a more successful concurrent run, although there were still failures, but I think it's a good first step.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.4, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054068#comment-13054068 ]
Knut Anders Hatlen commented on DERBY-5288:
-------------------------------------------
What are the memory settings for the JVMs (heap and permgen)? And how much memory is available on the machine?
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055675#comment-13055675 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
I merged revision 1138201 and 1138795 to SpawnedProcess.java from trunk to 10.8 (clean merge), then (because there were conflicts) manually backported the changes to 10.7 and 10.6 (which were identical before the change). I committed these changes (with revision 1140196 to 10.7 and merged back to 10.6 with revision 1140199) after I ran an experiment with ibm 1.5 and 1.6 (so no OOMs or PermGen errors) for each of these branches.
The results of this latest experiment were:
- no failures for 10.6 ibm 1.5 or 1.6
- 10.7 and trunk had 1 error for both 1.5 and 1.6, testReplication_Local_1_Indexing(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_1Indexing), each similar to DERBY-4635 (but apparently, the error can happen in more than one place).
- 10.8 had both an error like DERBY-4635, and a failure in testShutdownWhileScanningThenDelete(org.apache.derbyTesting.functionTests.tests.store.AutomaticIndexStatisticsTest) like DERBY-5108. According to the comments in that JIRA issue Kristian was planning to backport the changes from trunk to 10.8.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053298#comment-13053298 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
Your theory about the hangs make sense. And yes, your patch also allows the SecureServerTest to run concurrently (8 times, 4 different jvms).
I'll try a more involved test run, and if ok, I'll commit this patch (unless you prefer to do it).
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054096#comment-13054096 ]
Mike Matrigali commented on DERBY-5288:
---------------------------------------
For some context, were you able to do the same experiment before the change with the same environment and settings? Or is this a new test?
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055685#comment-13055685 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
Forgot to mention there were some additional stack traces, which apparently did not result in test errors or failures.
For instance, there was a 'java.net.SocketException: Connection reset' in both the 10.8 and trunk ibm1.5 runs in testReplication_Local_3_p5_DERBY_3878, which looks the same as one encountered by Kathey (as per a comment in DERBY-4565: https://issues.apache.org/jira/browse/DERBY-4564?focusedCommentId=12837564&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12837564).
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054140#comment-13054140 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
I was able to do this experiment with my small (but incorrect) change of revision 1138201 - but before the commit.
I will double check this by building after svn update -r 1138201 and rerunning the experiment. Takes about 8 to 10 hours. I'll check tomorrow on the result and post.
I'm not running with any special settings, so whatever is the default for the jvms is what gets picked up...
There's 3.87 GB of RAM.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056866#comment-13056866 ]
Myrna van Lunteren commented on DERBY-5288:
-------------------------------------------
Those test runs finished without trouble.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053752#comment-13053752 ]
Knut Anders Hatlen commented on DERBY-5288:
-------------------------------------------
All the regression tests ran cleanly with the patch in my environment, so I went ahead and checked it in.
Committed revision 1138795.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.5, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5288) running multiple suites.All
concurrently should be possible
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-5288:
--------------------------------------
Attachment: join-threads.diff
I think the join() call is misplaced. We should call join() right before we try to access the output, not when we start the process, as that won't let the test start until the process has completed (which is likely why a timeout was needed to prevent hangs).
Does the attached patch join-threads.diff preserve the improvements you saw with the original patch? This patch calls join() on places where we know the process has terminated, and we just need to let the threads that read stdout and stderr get enough time to complete before we check the output.
> running multiple suites.All concurrently should be possible
> -----------------------------------------------------------
>
> Key: DERBY-5288
> URL: https://issues.apache.org/jira/browse/DERBY-5288
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.1.4, 10.9.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-5288_1.diff, join-threads.diff
>
>
> When attempting to run multiple suites.All runs at the same time, using a different location & jvm & a different value for
> -Dderby.tests.basePort, there are still a few tests that fail regularly.
> The first one is SecureServerTest.
> See also the discussion on this thread: http://osdir.com/ml/derby-dev-db-apache/2011-06/msg00337.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira