Repository navigation
gh run view - only first attempt #5629
Description
Activity
The
gh run downloaddoes the same and we dont have an option to choose which attempt we want@mislav @samcoe @josebalius I don't mean to be a pest, but this has been
needs-triagefor two weeks. I'm happy to look at writing a PR for this (and the other issues I've submitted) once they're ready for work.@nyarly Thanks for the feature request and your patients. I am a bit confused as to the request though. When you trigger a new run using
run reruna new whole new run gets created with its own unique ID, if you want to view the new run you would need to specify the new ID. Is the feature request that you would like to use the previous run ID to view the new run?Hey @samcoe, thanks for checking in.
I'm running through this workflow again now just to check the UI:
> gh run rerun 10:49:54 - started ? Select a workflow run X Merge remote-tracking branch 'origin/main' into github-deployer-permissions-update, Test Cluster Config (github-deployer-permissions-update) 38m45s ago ✓ Requested rerun of run 2416587330 > gh run view 10:50:06 - started ? Select a workflow run [Use arrows to move, type to filter] > * Merge remote-tracking branch 'origin/main' into github-deployer-permissions-update, Test Cluster Config (github-deployer-permissions-update) 38m56s ago X Remove apiGroup value, Test Cluster Config (github-deployer-permissions-update) 47m49s ago ✓ Merge pull request #536 from my-org/github-deployer-permissions-update, Build Prod (main) 2h12m21s ago ✓ Merge pull request #536 from my-org/github-deployer-permissions-update, Build Demo (main) 2h12m21s ago X Merge pull request #536 from my-org/github-deployer-permissions-update, Build and Deploy QA (main) 2h12m21s agoWhat I'm seeing here is that there's only one "run" to select, which is consistent with the Web UI - there'd be one "run" with a dropdown of which numbered re-run you want to see. In the web version, though, the dropdown defaults to the latest iteration.
If there's a new run created byrerun, and that's why I can only view the "oldest" (because it's the only), then the other runs should appear in thegh run viewmenu, right? Or there should be a sub-menu to select which run I mean.As I'm recreating this flow, I'm noticing that when I choose the run this time, I get the current, in-progress run, which is more useful, but from prior experience, if there are only completed runs, I got the oldest one (or a random one? something.)
Elaborating a bit:
After that re-run completes:
gh run view ? Select a workflow run [Use arrows to move, type to filter] > X Merge remote-tracking branch 'origin/main' into github-deployer-permissions-update, Test Cluster Config (github-deployer-permissions-update) 1h48m32s ago X Remove apiGroup value, Test Cluster Config (github-deployer-permissions-update) 1h57m25s ago ✓ Merge pull request #536 from my-org/github-deployer-permissions-update, Build Prod (main) 3h21m57s ago ✓ Merge pull request #536 from my-org/github-deployer-permissions-update, Build Demo (main) 3h21m57s ago X Merge pull request #536 from my-org/github-deployer-permissions-update, Build and Deploy QA (main) 3h21m57s agoOnly one run listed to choose from, not two, and selecting the run that I re-ran:
X github-deployer-permissions-update Test Cluster Config #538 · 2416587330Which is the run ID of the initial run.
I hope this is clarifying the issue I'm encountering. It seems like @fl250144 is having a similar issue with
gh run downloadwhich I think uses a similar menu interface.Reacted by Fabricio LopesThanks for all the info. I managed to reproduce this and am looking into it further
Describe the bug
gh --version->2.10.1After re-running a job,
gh run viewreports the logs only from the first attempt, not the most recent (or allowing a choice of attempt runs.) This is very confusing when debugging a CI run.Steps to reproduce the behavior
Expected vs actual behavior
Expected to see most recent logs, or choose which attempt to see logs of.
Actually see only the oldest attempt's logs; because I'm expecting the most recent log run, spend hours debugging the wrong problem.
A clear and concise description of what you expected to happen and what actually happened.