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

Hudson commented on HBASE-29851:
--------------------------------

Results for branch branch-3
        [build #515 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/General_20Nightly_20Build_20Report/]








(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.4.1 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/515/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.2 {color}


> Add more directories to yetus skip-dirs
> ---------------------------------------
>
>                 Key: HBASE-29851
>                 URL: https://issues.apache.org/jira/browse/HBASE-29851
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0-beta-2, 2.6.5, 2.5.14
>
>
> Yetus has a feature of "module finding", where it will evaluate the set of 
> modules that require test execution based on what files are changed. Ours is 
> a maven project, so starting with a changed file, it walks up the directory 
> tree looking for the firs pom.xml it encounters -- this is the module that 
> needs testing for that file change. For directories that do not contain a 
> pom.xml file, this means it will walk up to the root pom and thus run all 
> tests for all modules. We currently omit `dev-support` so that changes to 
> these scripts don't result in a complete test run. However, we should do the 
> same for the new .github directory, as well as our `bin` and `conf` dirs.
> We should also, probably, exclude `src` where our docs live, but we have 
> special handling in the personality file for asciidoc files, so I want to 
> give that more investigation before proposing changes there.



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

Reply via email to