[JENKINS-31673] Broken reporting of exception

In hudson.tasks.junit.TestResult#parse (line 297), a DocumentException is caught and reported as a failing test.

Unfortunately, the failing test yields a broken "Test Report" page. Selecting the '+' symbol expands the error, but results in a 404 not found, so the details of the stack-trace are unavailable.

This effect is visible at this example.

Cheers,

Paul.

---
Originally reported by paulmillar, imported from: Broken reporting of exception

• status: Open
  
• priority: Major
  
• component(s): junit-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-11-26
  

Raw content of original issue

In hudson.tasks.junit.TestResult#parse (line 297), a DocumentException is caught and reported as a failing test.


Unfortunately, the failing test yields a broken "Test Report" page.  Selecting the '+' symbol expands the error, but results in a 404 not found, so the details of the stack-trace are unavailable.


This effect is visible at this example.


Cheers,


Paul.

• environment: Jenkins ver. 1.638

Start at hudson.tasks.junit.TestResult#parse, where DocumentException is reported as a failing test, and reproduce the broken Test Report behavior using the linked example. The work is done when expanding the reported failure no longer returns a 404 and the exception stack trace is available.

Written by the indexing model from the issue text.