-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test results are attributed to the wrong workflow #181
Comments
This is a known limitation of the GitHub Check Status API. GitHub attributes the Check Status to an arbitrary workflow, not the one that is running the action that calls the Check Status API. This is annoying, I know. See #12. |
Wow, that's quite a non-response from GitHub. Thanks, hope there will be something happening. I'll submit a support request too to get it on their radar more. |
Trimmed down version of their response, sounds more promising than is visible at github.community:
|
I guess this is the same issue: but with timings days apart. I have a failed scheduled nightly workflow run With a failed test in a job Which reports its annotations to the CI run of the last commit on master. The consequence of this is that I can't see the failed test info on the scheduled run until I click around and find the last master commit's annotations. |
I'm running into this issue now. Did anyone ever find a solution for this? It seems GitHub still didn't do anything about this limitation. |
The best workaround that community has come up with is https://github.com/orgs/community/discussions/24616#discussioncomment-5607870. |
My workflow setup: https://github.com/TWiStErRob/net.twisterrob.healthcheck/tree/master/.github/workflows
Which means that each result should be under the corresponding workflow that uses test-run.yml, but all of them are under CI:
TWiStErRob/net.twisterrob.healthcheck#9
or earlier in another commit it was all under Scheduled (since then I renamed the jobs):
The text was updated successfully, but these errors were encountered: