[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500226#comment-17500226
]
Sean Busbey commented on HBASE-26788:
-
wonderful diagnosis work.
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500202#comment-17500202
]
Nick Dimiduk commented on HBASE-26788:
--
FYI [~busbey]
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500201#comment-17500201
]
Nick Dimiduk commented on HBASE-26788:
--
Looking through the [installed
plugins|https://ci-hbase.apache.org/pluginManager/installed], it seems we have
the Checks API plugin installed but no Checks Implementation plugins installed.
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500192#comment-17500192
]
Nick Dimiduk commented on HBASE-26788:
--
This step is coming from [our
use|https://github.com/apache/hbase/blob/ccd908f2187379853093dbb6fd3aabb648343a85/dev-support/Jenkinsfile_GitHub#L253]
of the {{junit}} plugin to "Archive JUnit-formatted test results". The [junit
plugin|https://www.jenkins.io/doc/pipeline/steps/junit/] seems to have support
for [Checks API plugin|https://plugins.jenkins.io/checks-api/], the mechanism
by which Jenkins can publish actions results to Github. I guess we have not
configured something about the Checks API plugin at the stage where the junit
plugin runs, and thus we get this warning. Let me try disabling check
publication at the {{junit}} configuration.
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500160#comment-17500160
]
Nick Dimiduk commented on HBASE-26788:
--
I was looking at
https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4125/7/pipeline/18/
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500096#comment-17500096
]
Duo Zhang commented on HBASE-26788:
---
If you are talking about this build
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4119/4/testReport/
It is still SUREFIRE-1821, where we failed to read the xml output. It will be
fixed in 3.0.0-M6, as the maintainer said...
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
[jira] [Commented] (HBASE-26788) Fix or disable Checks API callback in builds
[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500094#comment-17500094
]
Duo Zhang commented on HBASE-26788:
---
Does this always happen?
> Fix or disable Checks API callback in builds
>
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
>Reporter: Nick Dimiduk
>Priority: Major
>
> 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)
