[
https://issues.apache.org/jira/browse/HBASE-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20364:
--------------------------------
Status: Patch Available (was: In Progress)
-v0
- update final build check so that "null" and "SUCCESS" are both treated as
success
- before doing scm checkout, write a commentfile for hte stage that will say
the stage failed if we don't overwrite it later.
[see nightly build with this change in
place|https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/HBASE-20364/2/]
Comment built (with WIP patch that fails each stage):
{code}
00:20:12.400 [INFO] Comment:
[Pipeline] echo
00:20:12.402 Results for branch HBASE-20364
00:20:12.402 [build #2 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20364/2/]:
(x) *{color:red}-1 overall{color}*
00:20:12.402 ----
00:20:12.402 details (if available):
00:20:12.402
00:20:12.402 (x) {color:red}-1 general checks{color}
00:20:12.402 -- Something went wrong running this stage, please [check relevant
console
output|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20364/2//console].
00:20:12.402
00:20:12.402
00:20:12.402
00:20:12.402
00:20:12.402 (x) {color:red}-1 jdk8 hadoop2 checks{color}
00:20:12.402 -- Something went wrong running this stage, please [check relevant
console
output|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20364/2//console].
00:20:12.402
00:20:12.402
00:20:12.402 (x) {color:red}-1 jdk8 hadoop3 checks{color}
00:20:12.402 -- Something went wrong running this stage, please [check relevant
console
output|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20364/2//console].
00:20:12.402
00:20:12.402
00:20:12.402 (x) {color:red}-1 source release artifact{color}
00:20:12.402 -- Something went wrong with this stage, [check relevant console
output|${BUILD_URL}/console].
00:20:12.402
{code}
no comment posted here because it was the first build so jenkins didn't think
anything had changed.
> 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
> Assignee: Sean Busbey
> Priority: Critical
> Attachments: HBASE-20364.0.patch
>
>
> 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)
