How do I access annotations for a previous attempt of a workflow? #103026
Replies: 2 comments 1 reply
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I'm trying to get statistics on how often we're seeing a certain failure in GitHub Actions runs. I should be able to use the Check Runs API to get the annotations for the workflow run. The problem is that people often re-run their CI checks when they see this failure, so the most recent attempt of the workflow is a success, and the API apparently only allows you to see the last check run output. (The web UI allows you to see all of the check runs.)
Here's an example:
python-3.8,django-pinned,lms-5
has the annotation "The self-hosted runner: edx-platform-openedx-ci-runner-deployment-7xdl7-twcfc lost communication with the server." If you switch to attempt # 2 using the UI, you'll see that it succeeded.https://api.github.com/repos/openedx/edx-platform/actions/runs/5476653975/attempts/1
and.../attempts/2
, the results differ in only a few places. Here are the important differences between the attempts:check_suite_url
, which only shows the successful checks from the second attempt. (They do have different log URLs, but the logs don't show this kind of failure.)https://api.github.com/repos/openedx/edx-platform/commits/ab3d322bc9/check-runs
) again shows this most recent check suite, but not the first attempt.GitHub clearly has this information, as it's shown in the UI. How can I get it via the API?
Edit: I've re-posted this as a Product Feedback, since it appears that this is just a bug in the API: https://github.com/orgs/community/discussions/124000
Beta Was this translation helpful? Give feedback.
All reactions