Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.6.0
-
None
Description
Intermittent failure in ExecutionCommandWrapperTest:
Running org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 14.452 sec <<< FAILURE! - in org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest testExecutionCommandHasVersionInfoWithoutCurrentClusterVersion(org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest) Time elapsed: 0.024 sec <<< ERROR! org.apache.ambari.server.ServiceNotFoundException: Service not found, clusterName=c1, serviceName=HDFS at org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest.testExecutionCommandHasVersionInfoWithoutCurrentClusterVersion(ExecutionCommandWrapperTest.java:293)
is caused by dependence on order of execution of test methods.
Steps to reproduce:
- Disable testGetExecutionCommand() to simulate "wrong" order of execution
- Run ExecutionCommandWrapperTest
Result:
Running org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.4 sec <<< FAILURE! - in org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest testExecutionCommandHasVersionInfoWithoutCurrentClusterVersion(org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest) Time elapsed: 0.011 sec <<< ERROR! org.apache.ambari.server.ServiceNotFoundException: Service not found, clusterName=c1, serviceName=HDFS at org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest.testExecutionCommandHasVersionInfoWithoutCurrentClusterVersion(ExecutionCommandWrapperTest.java:298)
Attachments
Attachments
Issue Links
- links to