Not seeing reports when PR is merged even though reports are generated about test-reporter HOT 14 OPEN

I think I might be seeing the same thing.

Here's a test report that was correctly generated and uploaded that doesn't show in the main view

It was working earlier and I was trying to work out what changed. Here's an older build where the report does show.

I wonder if it's because I turned on the CodeQL option in github between the two runs. It seems to add a new section, and the test report now seems to end up incorrectly under the codeql section instead of the build section.

And here's a newer PR run showing the test result in the right place https://github.com/timabell/schema-explorer/pull/65/checks?check_run_id=20998088207

from test-reporter.

I would say it's a correct behavior. The Test Result is not a job. It reports a check.

I'm not sure why GitHub displays it as a Job for the PR builds.

from test-reporter.

I think I might be seeing the same thing.

Here's a test report that was correctly generated and uploaded that doesn't show in the main view

It was working earlier and I was trying to work out what changed. Here's an older build where the report does show.

I wonder if it's because I turned on the CodeQL option in github between the two runs. It seems to add a new section, and the test report now seems to end up incorrectly under the codeql section instead of the build section.

And here's a newer PR run showing the test result in the right place https://github.com/timabell/schema-explorer/pull/65/checks?check_run_id=20998088207

This exact thing is happening to us here

from test-reporter.

I've now seen this issue show up on a (private) project that's not even using this report uploader.

Edit - think it was https://github.com/phoenix-actions/test-reporting which turns out to be a fork of this repo

from test-reporter.

I'd like to report/follow this too. I see the test reports show under the CodeQL section rather than the workflow it was part of

from test-reporter.

Okay I think my hunch is off, I think it must be something in my workflow file. Having done some more tidying up it's now back again, and I have no idea why. Here's a newer build of main that has it in the right place https://github.com/timabell/schema-explorer/actions/runs/7705131292/job/20998613617

from test-reporter.

Okay I'm even more confused, it's just done it again, and this one is exactly as the issue describes - the PR build is fine, and then the build on main has the report missing.

PR that demonstrates the behaviour: timabell/schema-explorer#65

• PR build, all fine => https://github.com/timabell/schema-explorer/actions/runs/7705540824/job/20999641752
• merge to main, ended up in wrong place again
  • Where it should be: https://github.com/timabell/schema-explorer/actions/runs/7705547883
  • Where it actually is: https://github.com/timabell/schema-explorer/runs/20999661642 (found by looking at test report step raw output)

Tracking issue on my repo: timabell/schema-explorer#64

from test-reporter.

the action produces 2 links:
https://repo/check-runs/12345
https://repo/runs/12345
first one throws an error
{
"message": "Not Found",
"documentation_url": "https://docs.github.com/rest/checks/runs#get-a-check-run"
}
the second one redirects to some weird place where the report is displayed.

from test-reporter.

I think I run into the same issue.

I would say it's a correct behavior. The Test Result is not a job. It reports a check.

How is the check bound to the workflow? I use a workflow named Test Report that calls the action, but it appears that the report is associated with a different workflow named, CodeQL.

from test-reporter.

I've seen the report being associated with multiple different workflows actually (I think it's associated with whatever finished first or something like that). On the PRs is definitely a bother but not really a big problem as the check still appears on the list, although as child job of whatever other workflows. However, for cron jobs is a bit more unfortunate, as the check does not appear on the list and the way to find it is to go to the test report action ouptut and click on the HTML link there.

Can anyone with a bit more knowledge about the actions interface give some pointers to look for the culprit?

from test-reporter.

Same issue for me, all newly generated reports are shown under an old run and not the current one.

from test-reporter.

Reporting the same. Check is bouncing across other workflows, though if you're making it as a required check for PR merge and it bounced, PR would never pass those checks as there would be waiting for results status.

from test-reporter.

+1 - Just added the action today and it is exactly what I was looking for, thank you! Same behavior, the job/Test Report is added to workflow based on commit number instead of the workflow run number.

Our team's preference is for the job/Test Report to be added to the current run number, regardless of commit.

from test-reporter.

I had a similar problem. Multiple reports are created in different jobs. Then I got the following view...

from test-reporter.