Skip to content

When a build job has a dot "." in it's name, test details fail to load in the UI

Summary

When a build job has a dot . in the name, clicking on the test details for a build job fails with "There was an error fetching the test suite."

Steps to reproduce

  1. Go here (https://gitlab.com/hachque/gitlab-test-report-bug-repro/-/pipelines/192867022/test_report) and click on "gather-test-results". Observe that the test results can be seen.
  2. Go here (https://gitlab.com/hachque/gitlab-test-report-bug-repro/-/pipelines/192890150/test_report) and click on "gather-test-results.-now-with-a-dot". Observe that you get the "There was an error fetching the test suite." error.

Example Project

I have set up an example project here: https://gitlab.com/hachque/gitlab-test-report-bug-repro

What is the current bug behavior?

The test results fail to load, with no indication to the user as to why.

What is the expected correct behavior?

The test results should load.

Relevant logs and/or screenshots

No error:

image

With error:

image

Output of checks

This bug happens on GitLab.com.

Alternate Issue

Summary

If there is a . in the job name, the JUnit test report cannot be loaded

Steps to reproduce

  1. Create job with . in the name with a junit artifact
  2. When the pipeline runs, view the test results and click into the details for this job

Example Project

https://gitlab.com/JackDunnNZ/junittest/-/pipelines/195538363/test_report

Clicking on "test1.0" will not work, clicking on "test" or "test1" will work

What is the current bug behavior?

A banner displays "There was an error fetching the test suite." and the UI shows "There are no test cases to display."

image

What is the expected correct behavior?

The details of the test suite should be displayed like the other jobs

image

Relevant logs and/or screenshots

The browser console shows a 404 error trying to access the following URL, which seems to be causing the problem:

https://gitlab.com/JackDunnNZ/junittest/-/pipelines/195538363/tests/test1.0.json?build_ids[]=761621362

Output of checks

This bug happens on GitLab.com

Edited by Ricky Wiens