[
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
