[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501240#comment-17501240
]
Hudson commented on HBASE-26788:
--------------------------------
Results for branch branch-1
[build #212 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-1/212/]:
(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-1/212//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-1/212//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-1/212//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Disable Checks API callback from test results in PRs
> ----------------------------------------------------
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
> Fix For: 2.5.0, 1.8.0, 2.6.0, 3.0.0-alpha-3, 2.4.11
>
>
> Often as not, PR builds will succeed but be reported on the PR as a failure.
> The reason is represented in Jenkins pipeline as a warning in the "Archive
> Junit-formatted test results", with the message
> {noformat}
> [2022-03-01T22:05:49.166Z] Recording test results
> [2022-03-01T22:05:50.627Z] [Checks API] No suitable checks publisher found.
> {noformat}
> This is confusing and discouraging to contributors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
