Test report fails to load if there are annotations
Closed this issue · 8 comments
Hello,
The JUnit Test Report fails to load if there are annotations on the test results.
The annotations appear on the job summary page ok, but when I try to open the test report, I get an "Oops" page from GitHub with a 500 response code.
Annotations on passed and failed tests cause this error. If there are no annotations, meaning all tests pass and annotate_notice is set to false, I can open the test report.
I believe this was working last week.
Is there a way to disable annotations on failed tests to unblock us so that we can view the test report?
@anhan32 how many test-cases do you have? maybe it exceeds the amount of annotations github can handle.
Please note that the annotate_notice only controls annotations for successful testcases.
Disabling it will still result in annotations being created for test failures
how many test-cases do you have? maybe it exceeds the amount of annotations github can handle.
20 tests, and 1 was failing at the time that was annotated.
Please note that the annotate_notice only controls annotations for successful testcases.
Disabling it will still result in annotations being created for test failures
Yup understood. I was using it as a controlled use case where the test report works and then doesn't work
@anhan32 ok. for 20 tests it should really not cause problems. As I see it working for much larger cases.
This could be a problem on GitHub itself maybe, as there is really no reason for it to not load for that amount.
For example the testcase here: https://github.com/mikepenz/action-junit-report/actions/runs/2991279127 loads normally
If you click on a specific job, it fails. For example https://github.com/mikepenz/action-junit-report/actions/runs/2991279127/jobs/4796481690
Oh wow. That's helpful. I'll investigate, and see if it may be due to a change we control
Ok, thanks for your quick response!