Skip to content

Correctly determine run started/elapsed timestamps - #5945

Merged
mislav merged 4 commits into
trunkfrom
run-started-fix
Jul 21, 2022
Merged

mislav merged 4 commits into
trunkfrom
run-started-fix

Conversation

@mislav

@mislav mislav commented Jul 14, 2022 •

Copy link
Copy Markdown
Contributor

This switches run list and run view commands to measure how long ago did the run happen by using run_started_at, which is the timestamp of the latest run in a series, instead of created_at, which is the timestamp of the first run.

Fixes #5931
Most likely fixes #5629

This switches `run list` and `run view` commands to measure how long ago
did the run happen by using `run_started_at`, which is the timestamp of
the latest run in a series, instead of `created_at`, which is the
timestamp of the first run.
@mislav
mislav requested a review from a team as a code owner July 14, 2022 17:33
@mislav
mislav requested review from samcoe and removed request for a team July 14, 2022 17:33
mislav added 2 commits July 19, 2022 18:02
This switches `run list` and `run view` commands to measure how long ago
did the run happen by using `run_started_at`, which is the timestamp of
the latest run in a series, instead of `created_at`, which is the
timestamp of the first run.
@mislav
mislav requested a review from vilmibm July 20, 2022 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

gh run list has incorrect "elapsed" values gh run view - only first attempt

3 participants