HTTP Status 400 – Bad Request error in test results

Hi there,

A screenshot from a test result is impossible to remote debug and is unlikely to be relevant to anyone but you. Try to always include these 3 things.

  1. what did you try? (Code samples, command lines, screenshots, videos, etc)
  2. what did happen? (Error messages, description, outputs, stuff)
  3. what did you expect to happen?

Otherwise, no one else can get into your context and you’ll have to have someone who is exactly knowledgeable come along.

Hi MarkEWaite,
As I am facing the same issue while migrating existing jenkins version into new version (2.401.1).
While clicking existing test results link its showing that bad request and malformed url.
I tired with disabling the CSRF protection.
Implemented the latest junit plugin version too.
The “junitResult.XML” file having the link, showing in UI.
While expanding those links am getting the error.
Please help me on this…

what did you try → Migration from old jenkins version, its too old (2.73.3)
what did happen →

what did you expect to happen → It has to work with the JUNIT plugins as like existing result set

Hi @prabu ,

I can’t duplicate the problem that you’re describing. You didn’t provide enough information for others to duplicate the problem. Without that additional information, it is quite rare that others are able to guess what might be causing the issue.

I’m leaving for 4 days of vacation, so I won’t be able to offer any help. You’re much more likely to receive help from me and from others if you provide enough information so that others can duplicate the issue that you are seeing. “How to report an issue” provides a detailed guide that lists the information needed

You may ask, “Why do I need to provide all that information?” You’re trying to persuade people who volunteer their time to give you some of that time. It is more persuasive for me when you show that you’ve taken the necessary steps to provide enough details so that others can duplicate the problem. When less information is provided, I’m less interested in helping.

@prabu have you upgraded your plugins too?
Are they all up to date?

Hi @poddingue ,
Yes I have upgraded my JUNIT plugin into the latest.
Some of them suggested to downgrade and validate, that one also I have checked.
Finally found the issue not related to the jenkins & its plugins,
Its related to the xunit junitResultSet creation. While creating having template in xls format.
Some changes did on that and able to see the logs now.
Issue has been fixed.
Thanks for your answer…