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
UT failure: panic: duplicate metrics collector registration attempted #104940
Comments
/assign #76956 is similar |
This comment has been minimized.
This comment has been minimized.
@pacoxu: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig instrumentation |
/triage accepted |
To fix it gracefully, we may refactor the code in A temporary workaround before refactoring it:
|
Three testings failed due to These testings are:
|
What are you guys doing here? What test is this? You cannot change the component-base metrics code base it is doing what it is supposed to be doing. Does this test suite involve multiple sequential runs of the same test? |
@logicalhan I think this is odd to change the component-base metrics code base. But the refactor to use You can try to reproduce it with
|
Oh, yes. This test suite involves multiple sequential runs of the same test to catch flakes. It uses
|
You can use
|
Failure cluster 1b410c50dc9c60031af5
https://storage.googleapis.com/k8s-triage/index.html?text=prometheus
Error text:
TestRecordOperation
TestRecordOperation
TestGetHistogramVecFromGatherer
Recent failures:
2021/9/4 上午2:00:19 ci-kubernetes-generate-make-test-count10
2021/9/3 下午8:00:05 ci-kubernetes-generate-make-test-count10
2021/9/3 下午2:00:15 ci-kubernetes-generate-make-test-count10
2021/9/3 上午7:59:43 ci-kubernetes-generate-make-test-count10
2021/9/3 上午1:59:22 ci-kubernetes-generate-make-test-count10
/kind failing-test
/sig testing
This may be related with prometheus/client_golang#716 \ prometheus/client_golang#733
The text was updated successfully, but these errors were encountered: