Skip to content

Add custom sampling context testcases #4579

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

Merged
merged 3 commits into from
Jul 14, 2025

Conversation

sentrivana
Copy link
Contributor

Noticed we don't actually have tests for whether custom attributes provided at span start appear in the sampling context. We were only testing if each integration adds some automatically.

@sentrivana sentrivana requested a review from a team as a code owner July 14, 2025 12:18
@sentrivana sentrivana merged commit f8d88bb into potel-base Jul 14, 2025
103 checks passed
@sentrivana sentrivana deleted the ivana/potel/custom-sampling-context-test-case branch July 14, 2025 12:27
Copy link

codecov bot commented Jul 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.88%. Comparing base (17d866a) to head (e60fad4).
Report is 1 commits behind head on potel-base.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@              Coverage Diff               @@
##           potel-base    #4579      +/-   ##
==============================================
- Coverage       84.88%   84.88%   -0.01%     
==============================================
  Files             158      158              
  Lines           15365    15365              
  Branches         2427     2427              
==============================================
- Hits            13043    13042       -1     
  Misses           1573     1573              
- Partials          749      750       +1     

see 1 file with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants