[
https://issues.apache.org/jira/browse/OOZIE-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848951#comment-16848951
]
Hadoop QA commented on OOZIE-3498:
----------------------------------
PreCommit-OOZIE-Build started
> TestOozieCLI testRetryWithRetryCount and testRetryForTimeout is flaky
> ---------------------------------------------------------------------
>
> Key: OOZIE-3498
> URL: https://issues.apache.org/jira/browse/OOZIE-3498
> Project: Oozie
> Issue Type: Sub-task
> Components: tests
> Affects Versions: trunk
> Reporter: Andras Salamon
> Assignee: Andras Salamon
> Priority: Major
> Attachments: OOZIE-3498-01.patch
>
>
> {{org.apache.oozie.client.TestOozieCLI.testRetryWithRetryCount}} and
> {{org.apache.oozie.client.TestOozieCLI.testRetryForTimeout}} unit tests
> failed with an assertion error.
> The two test methods assume that the error message contains the following
> string:
> {noformat}
> Error while connecting Oozie server. No of retries = 2. Exception =
> Connection refused{noformat}
> and
> {noformat}
> Error while connecting Oozie server. No of retries = 4. Exception =
> Connection refused{noformat}
> respectively.
> During the test run the error message was:
> {noformat}
> IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of
> retries = 2. Exception = Error while authenticating with endpoint:
> http://localhost:11/oozie/versions{noformat}
>
> These tests test the retry function, so I don't think that the exact error
> message is important.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
