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
I've seen several cases of the kube-burner job creating a new Gsheet for runs, even when there is no data populated within them. Not an urgent issue but it seems wasteful.
Perhaps we could take the data typically put in the new speadsheet and instead include it in the write-scale-ci-results job and put said data in additional columns?
I've seen several cases of the kube-burner job creating a new Gsheet for runs, even when there is no data populated within them. Not an urgent issue but it seems wasteful.
Example case: https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/scale-ci/job/e2e-benchmarking-multibranch-pipeline/job/kube-burner/586
The spreadsheet: https://docs.google.com/spreadsheets/d/16A-DNhYSuTmr_QnjbW2gEkd8T8W1_rwF4Mwha8ZYZMk/edit?usp=sharing
The text was updated successfully, but these errors were encountered: