The committers listed above are authorized under a signed CLA.

• ✅ login: chickenbreeder / name: chickenbreeder (a1e2f3a)

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.9%. Comparing base (6e1fbbe) to head (9808699).

@@           Coverage Diff           @@
##            main   #3256     +/-   ##
=======================================
- Coverage   82.9%   82.9%   -0.1%     
=======================================
  Files        130     130             
  Lines      27386   27350     -36     
=======================================
- Hits       22711   22675     -36     
  Misses      4675    4675             

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I asked Claude to see if there are many others here we could pick up. Not sure how useful this is, but it's probably worth trying to pick out other instances of this pattern we can clean up!

1. opentelemetry-zipkin/src/propagator/mod.rs:464-683
   • B3 propagator tests with extensive test data sets
   • Multiple nested loops for single/multi-header formats
   • Could consolidate 20+ test cases
2. opentelemetry-sdk/src/metrics/internal/exponential_histogram.rs
   - Multiple locations (555-664, 914-1072, 1141-1229)
   - Complex test data structures for bucket calculations
   - 30+ test cases across different test functions
3. opentelemetry-otlp/src/retry.rs:218-495
   - 10+ similar async test functions for retry logic
   - Each tests different scenarios (success, failure, timeout, throttling)
   - Perfect candidate for #[rstest] with #[case] attributes

@chickenbreeder let me know when you are ready with this!

Hey @chickenbreeder , did you want to do more of these, or should we review it as it is?

Hey @scottgerring. Sorry, I did not get around to do any further work on this.

Thank you for your contribution! This PR has been automatically marked as stale because it has not had activity in the last 14 days. This may be due to a delay in review on our side or awaiting a response from you; either is fine, and we appreciate your patience.

It will be closed in 14 days if no further activity occurs. Pushing a new commit or leaving a comment will remove the stale label and keep the PR open.

Closed as inactive. Thank you again for the contribution; please feel free to reopen this PR (or open a new one) if you'd like to continue the work.

As we worked on this together at a hackathon earlier this year, it would be cool to see this merged. I'll try rebase against main this week.