Conversation
The summary job listed the jobs of every attempt of its run. After a few re-runs that listing spans several pages, and GitHub's API answers some of those pages with a persistent 502, so every re-run of the summary failed (main run #335, four attempts). Listing the current attempt returns every job of the run in a listing that paginates cleanly. Jobs carried over from earlier attempts keep their own run_attempt, which summarize_sec_regress.py already uses to pick the latest attempt of each job and its result artifact.
Listing only the current attempt would look up every job under that attempt number, but after a re-run of failed jobs the unchanged jobs ran, and stored their results, under an earlier attempt. The step now lists attempts 1 through the current one. A job appears from the attempt it ran in onward, so its first appearance gives that attempt, and the summary keeps each job's latest attempt and reads the matching result artifact. Jobs re-run in different attempts are therefore each taken from their own last run.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The summary job listed the jobs of every attempt of its run. After a few re-runs that listing spans several pages, and GitHub's API answers some of those pages with a persistent 502, so every re-run of the summary failed (main run #335, four attempts).
Listing the current attempt returns every job of the run in a listing that paginates cleanly. Jobs carried over from earlier attempts keep their own run_attempt, which summarize_sec_regress.py already uses to pick the latest attempt of each job and its result artifact.