JUnit Test Report job does not appear in the workflow run

[liyaka]

Hi, we have a strange behavior that started lately - when there are failed tests, JUnit Test Report job does not appear in the workflow run:

We do get the summary, but no not job where we can see the details and the logs

The way we expect it to work is this (it used to work like this, nothing is changed in our configuration):

the configuration is simple:

- name: Publish Test Report
          uses: mikepenz/action-junit-report@v4
          if: success() || failure() # always run even if the previous step fails
          with:
            report_paths: 'report.xml'
            fail_on_failure: true
            summary: true
            detailed_summary: true

[mikepenz]

Good day.

This is a strange one. Does it maybe get added to a different check?
Nothing indicates that there was a change in the action, as the respective API is still called here: https://github.com/mikepenz/action-junit-report/blob/v4.3.1/src/annotator.ts#L99-L100

Could be some behavior change from GitHub's side 🤔

[liyaka]

I also tried to upgrade to v5, same result :(
What do you mean by "Does it maybe get added to a different check?" ?
Any suggestions? additional configuration?...

[mikepenz]

v5 only contains improvement to test suite handling and to the formatting of the summary.

For the different check I actually used the wrong wording. There's a long standing GitHub issue where reprots might be sent to the wrong build: #40

So I was wondering if that possibly happens in your case

[mikepenz]

Or a different thought (which would be weird that it does not fail doing the API request) - does the CI have all permissions required?

https://github.com/mikepenz/action-junit-report?tab=readme-ov-file#pr-run-permissions

[liyaka]

Or a different thought (which would be weird that it does not fail doing the API request) - does the CI have all permissions required?

Since it used to work (until about a week ago) I guess yes...

[liyaka]

For the different check I actually used the wrong wording. There's a long standing GitHub issue where reprots might be sent to the wrong build: #40

We also have runs on PR/main and some schedule runs as well, but in our case, the results are not going anywhere :(
I checked all runs for the same commit (usually it's only one), no results, only the summary as I mentioned in the description..

[mikepenz]

Running the tests on the action itself does still create the check. I am out of ideas, but the most likely would be permission issue, or something similar.

[liyaka]

I found now that the test report indeed appears in the wrong workflow run - we have build-test and another validation workflow that both run for PR, and tests report appears not with the tests, just like explained in this ticket #40
I our case it's a completely different workflow, not different runs of the same one...
Any updates on this one?
I understand there is still no fix, is there any workaround?

[mikepenz]

As far as I am aware there was no new update related to the issue from the GitHub side. Unless I missed some new API or some update in the meantime.

Closing this as #40 will be the correct place to have further updates.

Thank you for reporting back.