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

Hudson commented on HDDS-1790:
------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16903 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16903/])
HDDS-1790. Fix checkstyle issues in TestDataScrubber (elek: rev 
190e4349d77e7ae0601ff81a70c7569c72833ee3)
* (edit) 
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/dn/scrubber/TestDataScrubber.java


> Fix checkstyle issues in TestDataScrubber
> -----------------------------------------
>
>                 Key: HDDS-1790
>                 URL: https://issues.apache.org/jira/browse/HDDS-1790
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: test
>            Reporter: Nanda kumar
>            Assignee: Nanda kumar
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There are 4 Checkstyle issues in TestDataScrubber that has to be fixed
> {noformat}
> [ERROR] 
> src/test/java/org/apache/hadoop/ozone/dn/scrubber/TestDataScrubber.java:[157] 
> (sizes) LineLength: Line is longer than 80 characters (found 81).
> [ERROR] 
> src/test/java/org/apache/hadoop/ozone/dn/scrubber/TestDataScrubber.java:[161] 
> (sizes) LineLength: Line is longer than 80 characters (found 82).
> [ERROR] 
> src/test/java/org/apache/hadoop/ozone/dn/scrubber/TestDataScrubber.java:[167] 
> (sizes) LineLength: Line is longer than 80 characters (found 85).
> [ERROR] 
> src/test/java/org/apache/hadoop/ozone/dn/scrubber/TestDataScrubber.java:[187] 
> (sizes) LineLength: Line is longer than 80 characters (found 104).
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

Reply via email to