[ 
https://issues.apache.org/jira/browse/HADOOP-15498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492973#comment-16492973
 ] 

Hudson commented on HADOOP-15498:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14305 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14305/])
HADOOP-15498. TestHadoopArchiveLogs (#testGenerateScript, (inigoiri: rev 
8fdc993a993728c65084d7dc3ac469059cb1f603)
* (edit) 
hadoop-tools/hadoop-archive-logs/src/test/java/org/apache/hadoop/tools/TestHadoopArchiveLogs.java


> TestHadoopArchiveLogs (#testGenerateScript, #testPrepareWorkingDir) fails on 
> Windows
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-15498
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15498
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Anbang Hu
>            Assignee: Anbang Hu
>            Priority: Minor
>              Labels: Windows
>             Fix For: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.3
>
>         Attachments: HADOOP-15498-branch-2.001.patch, HADOOP-15498.000.patch, 
> HADOOP-15498.001.patch
>
>
> [TestHadoopArchiveLogs#testGenerateScript|https://builds.apache.org/job/hadoop-trunk-win/479/testReport/org.apache.hadoop.tools/TestHadoopArchiveLogs/testGenerateScript/]
>  fails on Windows because script generation uses "\n", but description uses 
> System.lineSeparator().
> [TestHadoopArchiveLogs#testPrepareWorkingDir|https://builds.apache.org/job/hadoop-trunk-win/479/testReport/org.apache.hadoop.tools/TestHadoopArchiveLogs/testPrepareWorkingDir/]
>  fails on Windows because according to [sticky bit 
> wiki|https://en.wikipedia.org/wiki/Sticky_bit], sticky bit is for Unix-like 
> system.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to