[
https://issues.apache.org/jira/browse/NUTCH-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Nagel resolved NUTCH-3129.
------------------------------------
Resolution: Duplicate
Likely a duplicate of NUTCH-3143, discovered few months later, Jan 2026 and
soon after.
> Investigate empty TEST-org.apache.nutch.util.TestMimeUtil.xml result
> --------------------------------------------------------------------
>
> Key: NUTCH-3129
> URL: https://issues.apache.org/jira/browse/NUTCH-3129
> Project: Nutch
> Issue Type: Test
> Components: ci/cd, jenkins, test
> Affects Versions: 1.22
> Reporter: Lewis John McGibbney
> Priority: Major
> Fix For: 1.23
>
>
> Since we upgraded to JUnit 5 (Jupiter) cf. NUTCH-2887, the Jenkins
> Nutch-trunk job
> ([https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/)|https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/]
> began indicate *_unstable_* ** status.
> The presence of an _*emty*_ JUnit report for
> [https://github.com/apache/nutch/blob/master/src/test/org/apache/nutch/util/TestMimeUtil.java]
> appears the be the reason.
> An example can be found below...
> [https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/lastCompletedBuild/testReport/TEST-org.apache.nutch.util.TestMimeUtil/xml/_empty_/]
> This task must investigate and provide some fix for the absent JUnit report.
> As of right now I have no idea why this is happening.
> For the time being I have essentially configured the Jenkins job to not fail
> due to this empty test so we need to remove that configuration once we find a
> fix. We also need to update the new junit-report.yaml
> ([https://github.com/apache/nutch/blob/master/.github/workflows/junit-report.yml])
> as it similarly has been configured to not fail the GitHub CI build for
> similar reasons.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
