-
Notifications
You must be signed in to change notification settings - Fork 39.6k
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
Revert "Update opentelemetry dependencies to the latest release." #125731
Conversation
LGTM label has been added. Git tree hash: c7fdef894a2512bd2e472f776eefb2bd218fa42d
|
Seems like this PR still hit #125688 (test run link) |
/test pull-kubernetes-unit |
cc @wojtek-t @p0lyn0mial @serathius for visibility that even with the grpc change reverted, the TestWatchSemantics test is still flaking. Is there another revert in flight that would address that?
|
heh.... @liggitt - let me try to open a PR to fix that, unless you want to revert it... |
I don't have time to chase it, feel free to revert or fixup |
Will open a fix in few minutes |
@dashpole: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
/retest [flake being fixed in https://github.com//pull/125733 ] |
Confirmed it's an issue with upgrading google.golang.org/grpc |
Issue first appears on grpc v1.64.0. We could consider upgrading opentelemetry assuming we can stay on grpc v1.63.0. |
https://github.com/grpc/grpc-go/releases/tag/v1.64.0
|
OMG they made String() non-deterministic |
/triage accepted |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Revert due to #125575 (comment)
Related to #125688
Special notes for your reviewer:
The PR could not be automatically reverted, so i've manually downgraded all dependencies updated by the PR
Does this PR introduce a user-facing change?