[
https://issues.apache.org/jira/browse/HBASE-28722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864746#comment-17864746
]
Hudson commented on HBASE-28722:
--------------------------------
Results for branch HBASE-28722
[build #2 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/HBASE-28722/2/]:
(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/HBASE-28722/2/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/HBASE-28722/2/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{color}
> Should wipe out all the output directories before unstash in nightly job
> ------------------------------------------------------------------------
>
> Key: HBASE-28722
> URL: https://issues.apache.org/jira/browse/HBASE-28722
> Project: HBase
> Issue Type: Bug
> Components: jenkins, scripts
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.10
>
>
> For master and branch-3, we do not have jdk8 and jdk11 stages but we can
> still see there are comments on jira which include these stages's results.
> I think the problem is that, in the 'init health results' stage, we want to
> stash some empty results but actually there are some build results for
> previous builds there so we stash some non empty results.
> We should wipe out these directories first before stash them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
