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

ASF GitHub Bot commented on HADOOP-19017:
-----------------------------------------

ayushtkn commented on PR #5820:
URL: https://github.com/apache/hadoop/pull/5820#issuecomment-1871233821

   Strange the linux build doesn't report any errors for license
   
https://ci-hadoop.apache.org/view/Hadoop/job/hadoop-qbt-trunk-java8-linux-x86_64/1453/console
   <img width="1311" alt="image" 
src="https://github.com/apache/hadoop/assets/25608848/8e4c7919-e323-4670-aef8-2dca80b4ed5b";>
   
   >  I'm hoping that we catch any regression with the things that are 
currently passing
   
   With these many failing tests, how will other developers figure out which 
one is a regression & which was already broken? You should put the proposal of 
enabling the Pre-Commit for Windows for each PR on the dev list, I believe & 
let folks know the current state of the build before enabling it
   
   For the code changes, it LGTM
   




> Setup pre-commit CI for Windows 10
> ----------------------------------
>
>                 Key: HADOOP-19017
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19017
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: build
>    Affects Versions: 3.4.0
>         Environment: Windows 10
>            Reporter: Gautham Banasandra
>            Assignee: Gautham Banasandra
>            Priority: Critical
>              Labels: Jenkins, pull-request-available
>
> We need to setup a pre-commit CI for validating the Hadoop PRs against 
> Windows 10.
> On a sidenote, we've got the nightly Jenkins CI running for Hadoop on Windows 
> 10 - 
> https://ci-hadoop.apache.org/view/Hadoop/job/hadoop-qbt-trunk-java8-win10-x86_64/.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to