-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
test: fix intermittent operator metrics test failure #12737
Conversation
Signed-off-by: william.vanhevelingen <william.vanhevelingen@acquia.com>
Follow-up to #12702 and #12730, for reference. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Signed-off-by: william.vanhevelingen <william.vanhevelingen@acquia.com>
Signed-off-by: william.vanhevelingen <william.vanhevelingen@acquia.com>
Due to the intentionally breaking changes in upstream protobuf, I would recommend refactoring your tests to render to proto and use the proto compare tooling. |
Signed-off-by: william.vanhevelingen <william.vanhevelingen@acquia.com>
See the more detailed comment in the upstream issue: prometheus/client_model#83 (comment), which links to more upstreams prometheus/client_golang#1323 and golang/protobuf#1121 I merged this for now as it was blocking CI intermittently, but indeed, that sounds like we may want to go with that route if it's more accurate. We'd have to analyze if it's worthwhile or if this workaround is "good enough" if we have to add more deps etc to do that |
Motivation
Fixes intermittent unit test failures
Modifications
Verification