You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a case where Re-run a job that once failed, it succeeds.
I think the last Attempt is probably being aggregated, but is it possible to aggregate all Attempts?
The text was updated successfully, but these errors were encountered:
@srz-zumix
GitHub provides attempts aware workflow_run and workflow_job API, so it possible to aggregate it.
However I designed GitHub Actions part of CIAnalyzer to not be aware of attempts, it seems not easy to support it.
CIAnalyzer can skip to fetch workflow that was already fetched in previous run, it relies on own metadata JSON file. Currently run_number is used to recognize which build was fetched in the last run, but run_number does not increment when you rerun workflow.
(Try gh api repos/Kesin11/ts-junit2json/actions/runs/6125855885/attempts/1 | jq .run_number and gh api repos/Kesin11/ts-junit2json/actions/runs/6125855885/attempts/2 | jq .run_number).
It should consider new way to skip fetched build in last run.
And I'm also worried about calculating workflow/job duration that uses various time fields (created_at, started_at etc...) correctly when workflow was retried.
I don't have enough motivation to solve this problem at the moment. But if you tackle this issue, I'd be happy to review it.
There is a case where Re-run a job that once failed, it succeeds.
I think the last Attempt is probably being aggregated, but is it possible to aggregate all Attempts?
The text was updated successfully, but these errors were encountered: