jenkinsci / jenkinsci/junit-plugin

[JENKINS-38336] REST for testReport in xml format throws error - Char 0x0 out of allowed range

Open
#1,044 0 comments 0 reactions 0 assignees View on GitHub
component:junit-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
87
Forks
351
Avg merge
1d 19h
Merged PRs (30d)
2

Description

When we access the testreport in the xml format of REST; there is the error "Char 0x0 out of allowed range" in the chrome browser. The data gets displayed with out any error with the json format.

There seems to be special character that are being added as part of the test case debug, this data when tries to get printed causes the error.

I believe the json is able to ignore the special character and not in case of xml.

I think the xml version being 1.0 may be causing this issue.

---
Originally reported by banu_prakash, imported from: REST for testReport in xml format throws error - Char 0x0 out of allowed range


  • status: Open
  • priority: Minor
  • component(s): junit-plugin
  • label(s): 0x0, testreport
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-11-26

Raw content of original issue

When we access the testreport in the xml format of REST; there is the error "Char 0x0 out of allowed range" in the chrome browser. The data gets displayed with out any error with the json format.
There seems to be special character that are being added as part of the test case debug, this data when tries to get printed causes the error.
I believe the json is able to ignore the special character and not in case of xml.
I think the xml version being 1.0 may be causing this issue.

  • environment: Jenkins Version - 1.580, Windows 7 64, Chrome 52,

1 attachment

- [error.png](https://issues.jenkins.io/secure/attachment/33996/error.png)
> ![error.png](https://issues.jenkins.io/secure/attachment/33996/error.png)

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reproducing the REST testReport request in XML format and compare it with the JSON response; done means the XML response handles the reported 0x0 character without the browser error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.