[
https://issues.apache.org/jira/browse/OOZIE-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Virag Kothari resolved OOZIE-804.
---------------------------------
Resolution: Fixed
> TestDecisionActionExecutor failing due to uninitialized conf
> ------------------------------------------------------------
>
> Key: OOZIE-804
> URL: https://issues.apache.org/jira/browse/OOZIE-804
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
> Assignee: Virag Kothari
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.574 sec <<<
> FAILURE!
> 5 testDecision(org.apache.oozie.action.decision.TestDecisionActionExecutor)
> Time elapsed: 7.422 sec <<< ERROR!
> 6 java.lang.NullPointerException
> 7 at
> org.apache.oozie.action.ActionExecutor.getOozieConf(ActionExecutor.java:293)
> 8 at
> org.apache.oozie.action.ActionExecutor.<init>(ActionExecutor.java:230)
> 9 at
> org.apache.oozie.action.ActionExecutor.<init>(ActionExecutor.java:218)
> 10 at
> org.apache.oozie.action.decision.DecisionActionExecutor.<init>(DecisionActionExecutor.java:39)
> 11 at
> org.apache.oozie.action.decision.TestDecisionActionExecutor.testDecision(TestDecisionActionExecutor.java:143)
> As part of oozie-796, the oozieConf is obtained in the constructor. The
> testcase needs to account for that by initializing the services.
> Also, currently we have surefire-2.7 which doesn't fail the build if the
> testcase 'errors' out. It only fails if the testcase has a 'failure'.
> This problem is solved by using surefire-2.12. However that is done as part
> oozie-783.
--
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
