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

ASF GitHub Bot commented on DRILL-5717:
---------------------------------------

Github user vvysotskyi commented on a diff in the pull request:

    https://github.com/apache/drill/pull/904#discussion_r147582266
  
    --- Diff: 
exec/java-exec/src/test/java/org/apache/drill/exec/fn/impl/TestDateFunctions.java
 ---
    @@ -34,19 +33,22 @@
     import org.apache.drill.exec.server.RemoteServiceSet;
     import org.apache.drill.exec.vector.ValueVector;
     import org.joda.time.LocalDate;
    -import org.joda.time.LocalTime;
     import org.joda.time.LocalDateTime;
    +import org.joda.time.LocalTime;
     import org.junit.Ignore;
     import org.junit.Test;
    -
     import com.google.common.base.Charsets;
     import com.google.common.io.Files;
     import org.junit.experimental.categories.Category;
     
    +import java.util.Locale;
    +
    +
     @Category({UnlikelyTest.class, SqlFunctionTest.class})
     public class TestDateFunctions extends PopUnitTestBase {
    --- End diff --
    
    This class has 4 space indentation, but according to our convention, it 
should be with 2 spaces. Since you have made changes here, could you please 
make 2 spaces indentation?



> change some date time unit cases with specific timezone or Local
> ----------------------------------------------------------------
>
>                 Key: DRILL-5717
>                 URL: https://issues.apache.org/jira/browse/DRILL-5717
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Tools, Build & Test
>    Affects Versions: 1.9.0, 1.11.0
>            Reporter: weijie.tong
>
> Some date time test cases like  JodaDateValidatorTest  is not Local 
> independent .This will cause other Local's users's test phase to fail. We 
> should let these test cases to be Local env independent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to