fix: otel-weaver flaky tests - #5562
Merged
Merged
Conversation
Signed-off-by: emdneto <9735060+emdneto@users.noreply.github.com>
lzchen
approved these changes
Aug 21, 2026
Pull request dashboard statusMerged · refreshed 2026-08-24 09:12 UTC Status above doesn't look right?
|
xrmx
approved these changes
Aug 24, 2026
Merged
via the queue into
open-telemetry:main
with commit Aug 24, 2026
f521707
579 of 580 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've noticed that
opentelemetry-test-utilstest suite is a bit flaky because of some weaver test failures:https://github.com/open-telemetry/opentelemetry-python/actions/runs/32396057250/job/96513062384
https://github.com/open-telemetry/opentelemetry-python/actions/runs/32351289717/job/96370826884
https://github.com/open-telemetry/opentelemetry-python/actions/runs/31783373109/job/94713791733
My understanding is because of open-telemetry/weaver#1626. I was able to reproduce the flaky test locally by running
uvx --with tox-uv tox -e py314-test-opentelemetry-test-utils -- -ra -k 'test_weaver_live_check'multiple times using weaver0.22.1. I installed weaver0.25.1and was not able to reproduce the issue anymore.