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 "Kathey Marsden (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 21:19:53 UTC
[jira] [Created] (DERBY-5601) Windows hang in NativeAuthentication
Windows hang in NativeAuthentication
-------------------------------------
Key: DERBY-5601
URL: https://issues.apache.org/jira/browse/DERBY-5601
Project: Derby
Issue Type: Bug
Components: Services, Test
Affects Versions: 10.9.0.0
Reporter: Kathey Marsden
Priority: Blocker
The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
....
emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
(emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
(emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
(net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
(net)lang.NativeAuthenticationServiceTest.testAll
and so no test continue and no results get posted to:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
The last run where this did not happen was:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
The actual command being executed is:
1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
ssword=yeeHaLdap -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
unctionTests.suites.All
I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209748#comment-13209748 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
I removed the runs before I saw this message.
I did, however, check for SpawnedProcess and it did not show up anymore with the latest patch.
I can run a suites.All run of the builds with and without your patch if you like to know the time difference, but that will take a while. I'll post that info in DERBY-5617.
In the mean time, I think *this* issue can be closed - perhaps 'invalid' is the best, or perhaps 'duplicate' as the cascading errors were a combination of my mistake and a jvm bug, the NativeAuthenticationTest and Interrupt errors are (being) addressed in different issues.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5601:
----------------------------------
Summary: Windows hang in NativeAuthenticationServiceTest testAll (was: Windows hang in NativeAuthentication )
> Windows hang in NativeAuthenticationServiceTest testAll
> -------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=yeeHaLdap -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll
Posted by "Kathey Marsden (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200098#comment-13200098 ]
Kathey Marsden commented on DERBY-5601:
---------------------------------------
Temporarily disabled the test to see if we can get tests running again. Dag reports infrastructure problems in the Oracle runs. There have been simultaneous infrastructure changes in the IBM recently which confused me thinking that was the reason, but clearly it is this test that has consistently been hanging since the Monday Jan 30, 1238138 run.
> Windows hang in NativeAuthenticationServiceTest testAll
> -------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=yeeHaLdap -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5601:
-----------------------------------
Attachment: (was: spawnedprocess_extended.diff)
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210111#comment-13210111 ]
Kristian Waagan commented on DERBY-5601:
----------------------------------------
It's not that important for me. If you have deleted the output, don't rerun the tests.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-5601:
--------------------------------------
Attachment: runsteall.out
I'm attaching the console output from one of the failed runs (this one included Kristian's latest patch, and a modified lang._Suite so it ran NativeAuthenticationServiceTest).
The test run on this machine with just DOS failed in the same test (NetworkServerControlAPITest.test_01_WrongUsage)
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Dag H. Wanvik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205942#comment-13205942 ]
Dag H. Wanvik commented on DERBY-5601:
--------------------------------------
May not be relevant at all, but Derby does use interrupts itself in NetworkServerControlImpl in three places.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207823#comment-13207823 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
The latest failures actually look like DERBY-4836. I'll check on my jvm version.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll
Posted by "Kathey Marsden (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201484#comment-13201484 ]
Kathey Marsden commented on DERBY-5601:
---------------------------------------
Posted this info on the list, but putting here to keep history in Jira. Myrna is investigating why cygwin upgrade may have caused this issue.
Talking with Myrna, Mike and Mamta and looking back at the onset of the NativeAuthenticationTest hang. I see that even at that time we had the prior SecureServerTest failure
(net)derbynet.SecureServerTest.testServerStartup used 6750 ms E.
(net)derbynet.SecureServerTest.testServerStartup used 46827 ms F.
Which we found later to have the stack Trace below [1] and which seemed to send things going down hill and led up to the hang, so may be related.
Myrna also told me at the the time this all started, she just switched over to cygwin from another shell program.
I have done suites.All runs sane and insane on my Windows machine as have Mike and Mamta and runs are clean, so I think it would be good to reenable NativeAuthenticationServiceTest on non-windows platforms and even on windows for non-ibm jvm's.
Myrna is working on figuring out why the cygwin upgrade caused such trouble on this machine. I will do this tomorrow unless someone else beats me to it.
Thanks
Kathey
[1] SecureServerTest( Opened = false, Authenticated= false, CustomDerbyProperties= null, WildCardHost= null )java.lang.InterruptedException
at org.apache.derbyTesting.junit.SpawnedProcess.complete(SpawnedProcess.java:184)
at org.apache.derbyTesting.junit.SpawnedProcess.complete(SpawnedProcess.java:146)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.runServerCommand(SecureServerTest.java:481)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.runsysinfo(SecureServerTest.java:411)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.testServerStartup(SecureServerTest.java:350)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:116)
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 junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> Windows hang in NativeAuthenticationServiceTest testAll
> -------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208369#comment-13208369 ]
Kristian Waagan commented on DERBY-5601:
----------------------------------------
Thanks for testing the SpawnedProcess patch, Myrna.
I've created DERBY-5617 to track that work.
If you still have the logs (stdout and stderr), do you mind grepping for '{SpawnedProcess}' and post whatever you find?
Also, did the test run take a lot longer than without the patch?
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Mike Matrigali (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205590#comment-13205590 ]
Mike Matrigali commented on DERBY-5601:
---------------------------------------
could you post the suites output of your current fail (just up and a little past the first failure is enough to get an idea of what tests are involved). If it is as before then the first error happens very quickly (i think you said 2-3 minutes), and less than 50 fixtures.
I think best next step is just do binary search to narrow down tests run by suite.all, hopefully eliminating most tests before the failure and still
coming up with reproducible case in your environment. At this point it seems like some test before the failing test is causing the issue, so narrowing down list of suspects would help.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Resolved] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-5601.
---------------------------------------
Resolution: Duplicate
I am marking this as a duplicate of DERBY-4836, because of the cascading errors after InternationalConnectTest.testBoundaries failure.
NativeAuthenticationTest issue has been fixed in DERBY-5608.
Using a later JVM version, I do not see an InterruptException, so that too is likely a jvm bug, or at least jvm-related.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5601:
----------------------------------
Description:
The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
....
emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
(emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
(emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
(net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
(net)lang.NativeAuthenticationServiceTest.testAll
and so no test continue and no results get posted to:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
The last run where this did not happen was:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
The actual command being executed is:
1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
unctionTests.suites.All
I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
Right now we have no reliable regression testing going on.
was:
The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
....
emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
(emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
(emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
(emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
(net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
(net)lang.NativeAuthenticationServiceTest.testAll
and so no test continue and no results get posted to:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
The last run where this did not happen was:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
The actual command being executed is:
1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
ssword=yeeHaLdap -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
unctionTests.suites.All
I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
Right now we have no reliable regression testing going on.
> Windows hang in NativeAuthenticationServiceTest testAll
> -------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5601:
-----------------------------------
Attachment: spawnedprocess_extended.diff
Attaching an extended version of SpawnedProcess, which isn't suspectible to interrupts when waiting for the process to complete.
I've let the uses of SpawnedProcess.complete behave as earlier, so if the interrupt seen earlier stopped us from waiting/destroying a process the test may now hang for 45 minutes before killing the process. For testing purposes you can set this to a lower value (use milliseconds) with derby.tests.process.killThreshold. This value must be higher than the time it takes to run the longest test using an external process, otherwise the process will be terminated prematurely. On a hang you should be able to use jstack to see where the code is waiting/stuck.
I've run suites.All with the patch on Windows Vista without errors, but there were no process-related issues in that run anyway.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205553#comment-13205553 ]
Kristian Waagan commented on DERBY-5601:
----------------------------------------
> I still see a multitude of failures though, so this issue cannot yet be closed.
Is it as bad as before, or is it somewhat better?
The hope was that those caused by shutdown errors would go away with the fix.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kathey Marsden (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205859#comment-13205859 ]
Kathey Marsden commented on DERBY-5601:
---------------------------------------
I wonder if it would be helpful to print
System.out.println("isInterrupted() value: " + Thread.currentThread().isInterrupted() );
in BaseTestCase.runBare()
I think that method is invoked for each test.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203474#comment-13203474 ]
Kristian Waagan commented on DERBY-5601:
----------------------------------------
Thanks for running the test again, Myrna.
I don't see anything in the output explaining the problem though.
The printing of stdout tells that the interrupt did happen (exit code = -1), but after the output has been read the process reports that it exited normally (exit code = 0).
I think there may be a few issues with the code in SpawnedProcess; it doesn't seem to explicitly close the process streams, waitFor may hang forever, and more importantly, it doesn't reset the interrupt flag. The latter may be what's causing the cascade error/failures.
I'll write a patch for testing on the machine experiencing this issue.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207855#comment-13207855 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
Sure enough, I was picking up the wrong version because of the different PATH setting syntax for cygwin. Hence the cascading errors after InternationalConnectTest.
Still, there was a hang in NativeAuthenticationServiceTest which Rick fixed, and I think the SpawnedProcess improvements are also valuable...So +1 to commit those changes.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205561#comment-13205561 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
Unfortunately, and puzzlingly, it's exactly the same (except for more tests run because I re-activated NativeAuthenticationServiceTest for this run).
I'm getting this behavior with just running:
java -Dderby.tests.trace=true junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All > outfile.out 2>&1
Here's the interrupt exception with this latest run:
-------------------
1) test_01_WrongUsage(org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlApiTest)java.lang.InterruptedException
at java.lang.ProcessImpl.waitFor(Native Method)
at org.apache.derbyTesting.junit.SpawnedProcess.complete(SpawnedProcess.java:215)
at org.apache.derbyTesting.junit.SpawnedProcess.complete(SpawnedProcess.java:176)
at org.apache.derbyTesting.junit.BaseTestCase.readProcessOutput(BaseTestCase.java:774)
at org.apache.derbyTesting.junit.BaseTestCase.assertExecJavaCmdAsExpected(BaseTestCase.java:508)
at org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlApiTest.test_01_WrongUsage(NetworkServerControlApiTest.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
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 junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
----------------------------
and the second and third failures are just as before.
Note that the interrupt error does occur now in a different test than when we first saw this.
It's still not happening when I run the derbynet._Suite by itself, only when running suites.All.
I'll do the following experiments over the weekend:
- run without the redirect to file 2>&1 (perhaps there's a problem lobbing stdout and stderr together?)
- run in a dos command shell
- get a smaller suites.All subset
- install a debugger and step through? (Probably won't get to this until Monday).
Any other suggestions on what I could do to gather more information?
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Issue Comment Edited] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Mike Matrigali (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207223#comment-13207223 ]
Mike Matrigali edited comment on DERBY-5601 at 2/13/12 10:12 PM:
-----------------------------------------------------------------
it built for me in a client using ibm16 in my path and ANT_JAVA set to jdk16, with nothing in my local.properties (most notably no jdk4lib* variable settings). Closable looks like it was introduced in 1.5, so probably will not compile when using a pre
1.5 compiler or compiler directive. I think there is some magic that needs to be put into directories that require higher than 1.5 to build. If I add the
jdk14* lib settings to my local.properties I see the errors Myrna reports.
I think this means that if we check the patch in that j2me based jvms no longer will be able to run tests that use SpawnedProcess. And if we check it
in, probably needs a change to the build.xml file in the junit directory indicating that it need jdk15 libs for that file.
was (Author: mikem):
it built for me in a client using ibm16 to compile. Closable looks like it was introduced in 1.5, so probably will not compile when using a pre
1.5 compiler or compiler directive. I think there is some magic that needs to be put into directories that require higher than 1.5 to build.
I think this means that if we check the patch in that j2me based jvms no longer will be able to run tests that use SpawnedProcess.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Rick Hillegas (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204826#comment-13204826 ]
Rick Hillegas commented on DERBY-5601:
--------------------------------------
I have set up an XP guest os under Virtual Box on my laptop. I have successfully run NativeAuthenticationServiceTest using the Windows versions of Java 5 and Java 6 from Oracle. The test did not hang for me. I ran the test against the state of the trunk after checking in the fix for DERBY-5607. It would be interesting to know if NativeAuthenticationServiceTest still hangs for you on your platform. Thanks.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204059#comment-13204059 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
I have been remiss - I did not pay proper attention to failures.
On the machine where I'm seeing trouble, with 10.8.2.2 and 10.9 alpha versions before revision 1159337, the suites.All fails *before* SecureServerTest: test_01_WrongUsage used 10969 ms E.
This is in test derbynet.NetworkServerControlApiTest.
The stack trace from the fail directory is similar to the interrupt error reported before:
---------------------------
[Error/failure logged at Wed Feb 08 13:46:35 PST 2012]
java.lang.InterruptedException
at org.apache.derbyTesting.junit.BaseTestCase.readProcessOutput(BaseTestCase.java:763)
at org.apache.derbyTesting.junit.BaseTestCase.assertExecJavaCmdAsExpected(BaseTestCase.java:507)
at org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlApiTest.test_01_WrongUsage(NetworkServerControlApiTest.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.textui.TestRunner.doRun(TestRunner.java:121)
at junit.textui.TestRunner.start(TestRunner.java:185)
at junit.textui.TestRunner.main(TestRunner.java:143)
---------------------------
So looks like this will happen at some point on a fast machine. Perhaps the check in of 1159337 improved matters, but didn't fix?
Myrna
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-5601:
----------------------------------
Summary: Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures (was: Windows hang in NativeAuthenticationServiceTest testAll)
Much conversation on this issue is occurring on the derby-dev list on the thread [URGENT] Critical test situation on trunk
http://old.nabble.com/-URGENT--Critical-test-situation-on-trunk-td33259629.html
Also changed summary to include prior errors/failures leading up to the hang
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207277#comment-13207277 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
I revised my properties and was able to get this to build...
I'll try out the patch and post the results.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207433#comment-13207433 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
The second version of spawnedprocess_extended.diff built without trouble in my original build environment, and has also past the NetworkServerControlApiTest.test_01_WrongUsage, and the SecureServerTest without hitting any failures.
The test run is still going, but it's looking good so far.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207155#comment-13207155 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
I appreciate all the effort put into this issue...
Unfortunately, I cannot build after installing the latest patch, I get:
[javac] C:\derby\trunk\java\testing\org\apache\derbyTesting\junit\SpawnedProcess.java:23: cannot find symbol
[javac] import java.io.Closeable;
[javac] ^
[javac] symbol: class Closeable
[javac] location: package java.io
[javac] C:\derbyt\trunk\java\testing\org\apache\derbyTesting\junit\SpawnedProcess.java:381: cannot find symbol
[javac] private void closeStream(Closeable stream) {
[javac] ^
[javac] symbol: class Closeable
[javac] location: class SpawnedProcess
[javac] 2 errors
[javac] Compile failed; see the compiler error output for details.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207819#comment-13207819 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
The good news is, the last run did not show any problems with SpawnedProcess.
I think the latest patch to SpawnedProcess etc. is good to commit.
Unfortunately, the run still keeled over in testBoundaries, as before, and had many failures after that, also as before, (apparently) because of Derby System Shutdown messages.
I'll see if I can analyze this failure further.
1) testBoundaries(org.apache.derbyTesting.functionTests.tests.jdbcapi.InternationalConnectTest)java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ001, SQLERRMC: java.security.AccessControlExceptionAccess denied (java.io.FilePermission [editedpath]\system\AAAA[...editedfilenameforformatting...]AAA\tmp delete)XJ001.U
at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:99)
at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:364)
at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:166)
at java.sql.DriverManager.getConnection(DriverManager.java:317)
at java.sql.DriverManager.getConnection(DriverManager.java:273)
at org.apache.derbyTesting.functionTests.tests.jdbcapi.InternationalConnectTest.testBoundaries(InternationalConnectTest.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
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:51)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:18)
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:51)
Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ001, SQLERRMC: java.security.AccessControlExceptionAccess denied (java.io.FilePermission [editedpath]\system\AAA[...editedfilenameforformatting...]AAA\tmp delete)XJ001.U
at org.apache.derby.client.am.Connection.completeSqlca(Connection.java:2125)
at org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(NetConnectionReply.java:538)
at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:431)
at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:294)
at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:121)
at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:826)
at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:762)
at org.apache.derby.client.net.NetConnection.flowUSRIDONLconnect(NetConnection.java:603)
at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:410)
at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:220)
at org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:74)
at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269)
at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:100)
... 41 more
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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] [Updated] (DERBY-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5601:
-----------------------------------
Attachment: spawnedprocess_extended.diff
Although I don't enjoy being stuck in the past, it wasn't my intension to break the J2ME support :)
I first thought my IDE had fooled me, but it turns out that it was because PropertySetter has been simplified. After that happened I have not manually configured my build system to catch these issues.
I've attached a new verrsion of the patch.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205790#comment-13205790 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
Forgot to mention; in the saved console output file I removed all failures and errors > 50, so there's stack traces of 50 errors and 50 failures.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Kristian Waagan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205601#comment-13205601 ]
Kristian Waagan commented on DERBY-5601:
----------------------------------------
I agree with Mike.
You could also move derbynet to the end of the run and see if it still happens then.
Another theory is that due to the interrupt the subprocess doesn't terminate and interferes with the tests. I'll have a patch for that soon...
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203384#comment-13203384 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
I used various old saved builds of derby and found the problem starts happening with builds including revision 1159337 (http://svn.apache.org/viewvc?view=revision&revision=1159337), and not before.
I also ran with Kristian's patch, which gives some output to the console:
(net)derbynet.SecureServerTest.testServerStartup START-SPAWNED:[-Demma.verbosity.level=silent, org.apache.derby.drda.NetworkServerControl, -p, 1527, sysinfo] STANDARD OUTPUT: exit code=-1
--------- Derby Network Server Information --------
Version: CSS10090/10.9.0.0 alpha - (1241655M) Build: 1241655M DRDA Product Id: CSS10090
derby.drda.maxThreads=0
derby.drda.sslMode=off
derby.drda.keepAlive=true
derby.drda.minThreads=0
derby.drda.portNumber=1527
derby.drda.logConnections=false
derby.drda.timeSlice=0
derby.drda.startNetworkServer=false
derby.drda.host=localhost
derby.drda.traceAll=false
[sysinfo output for revision 10.9.0.0 alpha - (1241655M)]
END-SPAWNED :[-Demma.verbosity.level=silent, org.apache.derby.drda.NetworkServerControl, -p, 1527, sysinfo] STANDARD OUTPUT:
used 5437 ms E.
(net)derbynet.SecureServerTest.testServerStartup used 13875 ms F.
(Soon) after this, I killed the java process
In the fail directory, this is the error stack:
[Error/failure logged at Tue Feb 07 16:02:19 PST 2012]
java.lang.InterruptedException: process exited with code 0
at org.apache.derbyTesting.junit.SpawnedProcess.complete(SpawnedProcess.java:234)
at org.apache.derbyTesting.junit.SpawnedProcess.complete(SpawnedProcess.java:150)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.runServerCommand(SecureServerTest.java:481)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.runsysinfo(SecureServerTest.java:411)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.testServerStartup(SecureServerTest.java:350)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:116)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.textui.TestRunner.doRun(TestRunner.java:121)
at junit.textui.TestRunner.start(TestRunner.java:185)
at junit.textui.TestRunner.main(TestRunner.java:143)
[Error/failure logged at Tue Feb 07 16:02:37 PST 2012]
junit.framework.AssertionFailedError: directory trace does not exist
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.setTraceDirectory(SecureServerTest.java:382)
at org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.testServerStartup(SecureServerTest.java:352)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:116)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
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.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at junit.textui.TestRunner.doRun(TestRunner.java:121)
at junit.textui.TestRunner.start(TestRunner.java:185)
at junit.textui.TestRunner.main(TestRunner.java:143)
derby.log is unexiting - just boots and shutdowns and stacks of
java.sql.SQLException: Database 'singleUse/oneuse0' not found.
and
java.sql.SQLException: Database 'testbase' not found.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Mike Matrigali (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207223#comment-13207223 ]
Mike Matrigali commented on DERBY-5601:
---------------------------------------
it built for me in a client using ibm16 to compile. Closable looks like it was introduced in 1.5, so probably will not compile when using a pre
1.5 compiler or compiler directive. I think there is some magic that needs to be put into directories that require higher than 1.5 to build.
I think this means that if we check the patch in that j2me based jvms no longer will be able to run tests that use SpawnedProcess.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207392#comment-13207392 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
The run with the first version of spawnedprocess_extended.diff - built with my local.properties modified from how I normally build - got past both tests that have shown problems before and is still happily chugging along.
So that's very promising - Thank You Kristian!
I'll interrupt that run now, pick up the latest patch, revert my build environment, and kick off a new run with the second version of that patch.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
> Attachments: runsteall.out, spawnedprocess_extended.diff
>
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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-5601) Windows hang in
NativeAuthenticationServiceTest testAll with prior interrupt error in
SecureServerTest and other cascade errors and failures
Posted by "Myrna van Lunteren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205532#comment-13205532 ]
Myrna van Lunteren commented on DERBY-5601:
-------------------------------------------
Rick, I ran with a recent build (including Christian's interrupt flag reset for DERBY-5608) but with the NativeAuthenticationServiceTest re-enabled for windows and found no hang. It looks like the hang is gone, and the test can be re-enabled.
I still see a multitude of failures though, so this issue cannot yet be closed.
> Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5601
> URL: https://issues.apache.org/jira/browse/DERBY-5601
> Project: Derby
> Issue Type: Bug
> Components: Services, Test
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Blocker
>
> The IBM Windows runs on trunk have been hanging in NativeAuthenticationServiceTest. This is preventing tests from continuing or being posted. The actual test run hangs at :
> ....
> emb)lang.AutoIncrementTest.test_4437_03_deferredInsert used 218 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_4589 used 6859 ms .
> (emb)lang.HalfCreatedDatabaseTest.test_5526 used 16 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 24061 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 17781 ms .
> (emb)lang.NativeAuthenticationServiceTest.testAll used 11187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll used 18187 ms .
> (net)lang.NativeAuthenticationServiceTest.testAll
> and so no test continue and no results get posted to:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1239981.html
> The last run where this did not happen was:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testSummary-1236968.html
> The actual command being executed is:
> 1 4748 2676 0 20:23:24 CONIN$ 46:30 C:\WINDOWS\system32\java.exe -Dder
> byTesting.ldapServer=socket.usca.ibm.com -DderbyTesting.ldapPort=389 -DderbyTest
> ing.dnString=oakland.ibm.com -DderbyTesting.ldapUser=mamta -DderbyTesting.ldapPa
> ssword=xxxxx -Xmx512M -Dderby.tests.networkServerStartTimeout=480 -Dderby.te
> sts.basePort=3100 -Dderby.tests.trace=true -DderbyTesting.oldReleasePath=d:/jart
> est/releases_for_upgrade_tests junit.textui.TestRunner org.apache.derbyTesting.f
> unctionTests.suites.All
> I couldn't reproduce this running the single test on my machine. Marking this blocker as the Oracle Nightlies seem to be having serious issues too that date back further.
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/Limited/
> Right now we have no reliable regression testing going on.
--
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