Test report randomly appears under different workflow

[Piedone]

With v8 of the action, we've noticed that sometimes the test reports will appear not under the workflow they were created from, but another workflow that runs in parallel on the same trigger.

The two workflows:

• build-and-test: This runs test-reporting for .NET builds. Two jobs run two builds (matrix builds, under Ubuntu and Windows) in parallel. The workflow utilizes an external reusable workflow, and where in the end test-reporting is called is here.
• validate-pull-request: This doesn't use test-reporting.

What we see:

• This build-and-test run is correct, the test reports appear there. This is the corresponding validate-pull-request run and this is also correct, no test reports there.
• This build-and-test run happened 5 minutes before the above one, without changing to the workflows. As you can see, the test reports are not there. They are, instead, under this is the corresponding validate-pull-request run.

This seems to be a bug to me. Note that the two workflows are unrelated apart from having an overlap of triggers.

Before we had the validate-pull-request workflow, we noticed test reports randomly missing, which is perhaps the same issue.

[IanMoroney]

So, this actually relates to a long-standing github issue, where the requesting run id isn't linked to the check suite id.
It's discussed here in detail:
dorny/test-reporter#67

[Piedone]

I see, thanks for explaining. How about then, as a stopgap workaround, do what's mentioned here? It would even be enough to include the "Check run HTML" link in the run summary.

#21 is about something similar.

[IanMoroney]

yep!
merged :)

[Piedone]

Thank you!