[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227882#comment-15227882
]
abhishek bafna commented on OOZIE-2496:
---------------------------------------
The Testcase execution got timeout in the Jenkins. There is no logical changes
in the patch-02. In the patch-02, moved all the three statements, containing
more than 132 characters, to the next line. I have checked the testcase
locally, it is working fine.
> Testcase failure due to environment specific line.separator value
> -----------------------------------------------------------------
>
> Key: OOZIE-2496
> URL: https://issues.apache.org/jira/browse/OOZIE-2496
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Environment: Windows
> Reporter: abhishek bafna
> Labels: patch
> Attachments: OOZIE-2496-01.patch, OOZIE-2496-02.patch
>
>
> The "line.separator" returns operating system specific line separator. The
> following testcase uses hard coded "\n" while comparing the return values in
> the assertion, which makes them to fail on the windows environment.
> {noformat}
> org.apache.oozie.client.TestOozieCLI#testOozieStatus
> org.apache.oozie.client.TestOozieCLI#testServerBuildVersion
> org.apache.oozie.client.TestOozieCLI#testClientBuildVersion
> {noformat}
> In the following testcase, we are using "line.separator" where as
> _TimestampedMessageParser_ sends the logs after appending "\n".
> {noformat}
> org.apache.oozie.util.TestXLogUserFilterParam#testloglevel_DEBUF_INFO
> org.apache.oozie.util.TestXLogUserFilterParam#testloglevel_Error
> org.apache.oozie.util.TestXLogUserFilterParam#testTextSearch
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)