prow.k8s.io job history page showing months-stale results #34312
Labels
area/prow
Issues or PRs related to prow
kind/bug
Categorizes issue or PR as related to a bug.
sig/k8s-infra
Categorizes an issue or PR as relevant to SIG K8s Infra.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
Comments
k8s-ci-robot
added
sig/testing
|
(was looking into kubernetes/kubernetes#129848) |
|
/area prow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
go from: https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-default&width=20
to this recent run: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/1889411351940435968
click the "Job History" link:
https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce
Observe that while the run was from today (feb 11) the job history page is showing results from December.
I suspect a bad metadata file?
I tried https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce?buildId=1889411351940435968 with no success
What you expected to happen:
Job history page should start with recent results.
How to reproduce it (as minimally and precisely as possible):
see above
Please provide links to example occurrences, if any:
see above
Anything else we need to know?:
I haven't noticed this on any other jobs yet
/sig testing k8s-infra
The text was updated successfully, but these errors were encountered: