[
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
