-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prow.k8s.io job history page showing months-stale results #34312
Comments
(was looking into kubernetes/kubernetes#129848) |
/area prow |
$ gsutil cat gs://kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/latest-build.txt
189489678293716582 But the page starts at 1868710627107672064 from december. Testgrid goes up to 1894896782937165824 as the currently running job. |
Huh, when I refresh I'm getting different results at https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce Each subsequent load has had newer results. I'm up to mid january ... |
It's not quite reliably loading newer runs on subsequent loads but they have averaged newer, They're reliably at least the current month now (still weeks old). Very strange ... |
Thanks! The last few times we've had issues with prow.k8s.io we've eventually root-caused them to migrating the CI to SIG K8s Infra and configuration issues etc so I didn't want to jump to filing a prow bug this time :-) |
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: