[#SFOS-1107] Intermittent Test Failure in HadoopConfigurationTest. Race condition?

SmartFrog

Intermittent Test Failure in HadoopConfigurationTest. Race condition?

Created: 10/Feb/09 11:15 AM (GMT) Updated: 10/Feb/09 06:08 PM (GMT)

Return to search

Component/s:

_service_hadoop

Affects Version/s:

3.17.010

Fix Version/s:

3.17.010

Time Tracking:

Not Specified

Environment:

elitebook running linux, 2 core system

Compatibility:

unknown

Description

« Hide

I'm getting an intermittent failure on
org.smartfrog.services.hadoop.test.system.conf.HadoopConfigurationTest

testEmptyConf Error Test failed (unknown) -TestCompletedEvent at Tue Feb 10 11:03:49 GMT 2009 alive: true status: Termination Record: HOST annecy:rootProcess:testEmptyConf:tests, type: normal, description: Empty Sequence succeeded:false forcedTimeout:false skipped:false

org.smartfrog.test.TerminationRecordException: Test failed
(unknown) -TestCompletedEvent at Tue Feb 10 11:03:49 GMT 2009 alive: true
status:
Termination Record: HOST annecy:rootProcess:testEmptyConf:tests, type: normal, description: Empty Sequence
succeeded:false
forcedTimeout:false
skipped:false
Termination Record: HOST annecy:rootProcess:testEmptyConf:tests, type: normal, description: Empty Sequence
at org.smartfrog.test.DeployingTestBase.completeTestDeployment(DeployingTestBase.java:315)
at org.smartfrog.test.DeployingTestBase.runTestsToCompletion(DeployingTestBase.java:338)
at org.smartfrog.test.DeployingTestBase.expectSuccessfulTestRun(DeployingTestBase.java:424)
at org.smartfrog.services.hadoop.test.system.conf.HadoopConfigurationTest.testEmptyConf(HadoopConfigurationTest.java:44

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Steve Loughran added a comment - 10/Feb/09 11:17 AM (GMT)

the test run deploys a component then an empty test sequence:

testEmptyConf extends ExpectDeploy {

  action extends EmptyHadoopConfiguration {
    conf.dump CONF_DUMP ;
  }

  tests extends Sequence {


  }
}

It is failing with empty sequence/succeeded=false. Question is, why?
The Empty Sequence message implies the test sequence has finished, this triggered the termination. We could try adding an assertion into the sequence to see if the imposition of work makes the test runner start up differently

[ Permlink | « Hide ]

Steve Loughran added a comment - 10/Feb/09 06:08 PM (GMT)

added a delay and its gone away