Skip to content

Conversation

@afinn12
Copy link
Contributor

@afinn12 afinn12 commented Nov 18, 2024

Needed

Description

image

  • 1 = first run, 3 = latest run
  • Clicking on the OverlayPanel takes you to the job in the specific attempt for the run
    • If a URL wasn't found (usually because the job was skipped), it's the URL for just the attempt, not the job.
  • Runs + Reruns = total runs
    • Should reruns be 6 or 10? (if rerun, do we count the first attempt as a rerun?)

Testing

  • Tested in dev
  • Tested in prod
    • Used data from our forked repo instead since data hasn't been updated in this repo yet

@afinn12 afinn12 marked this pull request as ready for review November 18, 2024 21:19
@afinn12 afinn12 mentioned this pull request Nov 18, 2024
4 tasks
@afinn12 afinn12 force-pushed the reruns branch 2 times, most recently from 27f0d58 to a3207df Compare December 6, 2024 19:19
Added a script that fetches PR data and created a separate view on the dashboard.
Tweaked dotenv require.

Fixes kata-containers#1

Signed-off-by: Anna Finn <[email protected]>
Added code to get rerun information to both fetch scripts.
Display the reruns as a superscript in the rowExpansionTemplate with the result/URL.

Fixes: kata-containers#8

Signed-off-by: Anna Finn <[email protected]>
@stevenhorsman
Copy link
Member

@sprt - do you know if there is much hope on progressing this as I've seen a few occasions where our dashboard is hiding some of the job instable due to re-runs going green?

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.

2 participants