ci(l1): fix "Unknown job" job message when workflow fails. #5089
+73
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
All failing workflows are showing "Unknown job" in Slack message
Description
The culprit was how we gathered the job list: we queried the generic listJobsForWorkflowRun, which sometimes returns an empty set for the latest attempt of a run. By switching to the attempt-specific endpoint and paging it ourselves, the script now pulls the jobs that actually failed before formatting the message, so the alert should finally show the real job names instead of defaulting to “Unknown job.”