[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406355#comment-15406355
]
Robert Kanter commented on OOZIE-2496:
--
+1
GWT is only used for the workflowgenerator, which nobody's really updated in at
least 3 years. Looks like gwt-links comes from googlecode.com, which is down
now. I'll create a JIRA proposing we drop workflowgenerator.
> 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
>Assignee: abhishek bafna
> Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2496-01.patch, OOZIE-2496-02.patch,
> OOZIE-2496-03.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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405608#comment-15405608
]
abhishek bafna commented on OOZIE-2496:
---
testcase failure is not related.
{noformat}
-1 COMPILE
-1 HEAD does not compile
-1 patch does not compile
{noformat}
The above failure are because of unable to download maven dependency for
{{gwt-links}}. This is happening very frequently for last couple of weeks.
> 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
>Assignee: abhishek bafna
> Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2496-01.patch, OOZIE-2496-02.patch,
> OOZIE-2496-03.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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405526#comment-15405526
]
Hadoop QA commented on OOZIE-2496:
--
Testing JIRA OOZIE-2496
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1792
.Tests failed: 6
.Tests errors: 2
.The patch failed the following testcases:
.
testCoordStatus_Failed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
. testMain(org.apache.oozie.action.hadoop.TestHiveMain)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
. testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
. testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
. testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3176/
> 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
>Assignee: abhishek bafna
> Labels: patch
> Attachments: OOZIE-2496-01.patch, OOZIE-2496-02.patch,
> OOZIE-2496-03.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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405338#comment-15405338
]
abhishek bafna commented on OOZIE-2496:
---
[~rkanter] Thanks for reviewing. Incorporated the suggestions. Also added a
{{SYSTEM_LINE_SEPARATOR}} constant into the {{XTestCase}} class, so that any
test class can reference it in future.
> 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
>Assignee: 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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405015#comment-15405015
]
Robert Kanter commented on OOZIE-2496:
--
This seems fine to me. However, I'm concerned about the overhead of having to
call {{System.getProperty("line.separator")}} so much; it's in a while loop.
Perhaps we should cache the value in a static variable? The tests don't really
matter, so it's mainly just {{TimestampedMessageParser}}.
> 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
>Assignee: 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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396898#comment-15396898
]
Hadoop QA commented on OOZIE-2496:
--
Testing JIRA OOZIE-2496
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/3112/
> 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
>Assignee: 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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224262#comment-15224262
]
Hadoop QA commented on OOZIE-2496:
--
Testing JIRA OOZIE-2496
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2809/
> 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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222722#comment-15222722
]
abhishek bafna commented on OOZIE-2496:
---
The failed testcases are not relevant.
> 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
>
>
> 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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222699#comment-15222699
]
Hadoop QA commented on OOZIE-2496:
--
Testing JIRA OOZIE-2496
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 3 line(s) longer than 132
characters
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1768
.Tests failed: 2
.Tests errors: 0
.The patch failed the following testcases:
.
testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker)
.
testLastOnlyMaterialization(org.apache.oozie.command.coord.TestCoordMaterializeTransitionXCommand)
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2807/
> 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
>
>
> 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)
[jira] [Commented] (OOZIE-2496) Testcase failure due to environment specific line.separator value
[
https://issues.apache.org/jira/browse/OOZIE-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221694#comment-15221694
]
abhishek bafna commented on OOZIE-2496:
---
In the _TestOozieCLI_ instead of using the hard coded "\n", updated with
System.getProperty("line.separator");
The _TimestampedMessageParser_, appends the "\n" for each message. Used
System.getProperty("line.separator") instead of hard coded "\n".
Please review the attached patch.
> 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
> Attachments: OOZIE-2496-01.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)
