avijitbasak commented on pull request #197:
URL: https://github.com/apache/commons-math/pull/197#issuecomment-922933961


   The following errors have been received after build. These are due to 
formatting of lambda expression. Need help to resolve this.
   [INFO] There are 6 errors reported by Checkstyle 8.29 with 
/home/travis/build/apache/commons-math/commons-math4-genetics/../src/main/resources/checkstyle/checkstyle.xml
 ruleset.
   [ERROR] 
src/test/java/org/apache/commons/math4/genetics/selection/TournamentSelectionTest.java:[51]
 (indentation) Indentation: 'block' child has incorrect indentation level 16, 
expected level should be 20.
   [ERROR] 
src/test/java/org/apache/commons/math4/genetics/selection/TournamentSelectionTest.java:[52]
 (indentation) Indentation: 'block rcurly' has incorrect indentation level 12, 
expected level should be 16.
   [ERROR] 
src/test/java/org/apache/commons/math4/genetics/dummy/DummyChromosome.java:[27] 
(indentation) Indentation: 'block' child has incorrect indentation level 12, 
expected level should be 16.
   [ERROR] 
src/test/java/org/apache/commons/math4/genetics/dummy/DummyChromosome.java:[28] 
(indentation) Indentation: 'block rcurly' has incorrect indentation level 8, 
expected level should be 12.
   [ERROR] 
src/test/java/org/apache/commons/math4/genetics/utils/ChromosomeRepresentationUtilsTest.java:[114]
 (indentation) Indentation: 'block' child has incorrect indentation level 20, 
expected level should be 12.
   [ERROR] 
src/test/java/org/apache/commons/math4/genetics/utils/ChromosomeRepresentationUtilsTest.java:[115]
 (indentation) Indentation: 'block rcurly' has incorrect indentation level 16, 
expected level should be 8.
   [INFO] 
------------------------------------------------------------------------
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to