db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5601) Windows hang in NativeAuthenticationServiceTest testAll with prior interrupt error in SecureServerTest and other cascade errors and failures
Date Fri, 10 Feb 2012 18:12:59 GMT

    [ 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

        

Mime
View raw message