[
https://issues.apache.org/jira/browse/NUTCH-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044390#comment-18044390
]
Hudson commented on NUTCH-3126:
-------------------------------
SUCCESS: Integrated in Jenkins build Nutch » Nutch-trunk #207 (See
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/207/])
NUTCH-3126 Report JUnit test results in GitHub pull request thread (#868)
(github:
[https://github.com/apache/nutch/commit/7b5ed23a528829d06a79280dc15a8f0fbb21f7f6])
* (edit) .github/workflows/junit-report.yml
> Report JUnit test results in GitHub pull request thread
> -------------------------------------------------------
>
> Key: NUTCH-3126
> URL: https://issues.apache.org/jira/browse/NUTCH-3126
> Project: Nutch
> Issue Type: Task
> Components: ci/cd, test
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Minor
> Fix For: 1.22
>
>
> It can be difficult to tell which test(s) make a Nutch build unstable through
> errors or failures.
> The [JUnit Report
> Action|https://github.com/marketplace/actions/junit-report-action] can be
> used to report JUnit test results as a check in the GitHub pull request which
> would provide the benefit of identifying exactly which line of test code
> produced an anomaly and what the anomaly is.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
