Sean Busbey created HBASE-20364:
-----------------------------------
Summary: nightly job gives old results or no results for stages
that timeout on SCM
Key: HBASE-20364
URL: https://issues.apache.org/jira/browse/HBASE-20364
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 3.0.0
Reporter: Sean Busbey
seen in the branch-2.0 nightly report for HBASE-18828:
{quote}
Results for branch branch-2.0
[build #143 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143/]:
(x) *\{color:red}-1 overall\{color}*
----
details (if available):
(/) \{color:green}+1 general checks\{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/140//General_Nightly_Build_Report/]
(/) \{color:green}+1 jdk8 hadoop2 checks\{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) \{color:green}+1 jdk8 hadoop3 checks\{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/143//JDK8_Nightly_Build_Report_(Hadoop3)/]
{quote}
-1 for the overall build was correct. build #143 failed both the general check
and the source tarball check.
but in the posted comment, we get a false "passing" that links to the general
result from build #140. and we get no result for the source tarball at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
