We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In some of the newly introduced storage tests, pod_startup_latency summaries aren't generated.
E.g. in this run: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-storage-scalability-max-configmap-vol-per-pod/1153307037698887684/ clearly it was measured, it was even logged as violated, but no .json file exists
What is interesting, in other tests sharing the same test-config (just different overrides), it works fine, e.g.: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-storage-scalability-max-emptydir-vol-per-pod/1153307037698887682/
The text was updated successfully, but these errors were encountered:
@mucahitkurt - this is the problem you had
Sorry, something went wrong.
hmm - I think I see what is happening - let me send a PR.
wojtek-t
Successfully merging a pull request may close this issue.
In some of the newly introduced storage tests, pod_startup_latency summaries aren't generated.
E.g. in this run:
https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-storage-scalability-max-configmap-vol-per-pod/1153307037698887684/
clearly it was measured, it was even logged as violated, but no .json file exists
What is interesting, in other tests sharing the same test-config (just different overrides), it works fine, e.g.:
https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-storage-scalability-max-emptydir-vol-per-pod/1153307037698887682/
The text was updated successfully, but these errors were encountered: