Ignore flaky opentelemetry-jaeger tests

[mattbodd]

Fixes #1505
Two tests have been intermittently failing from the opentelemetry-jaeger crate:
exporter::config::collector::http_client::collector_client_tests::test_bring_your_own_client
exporter::config::collector::tests::test_collector_exporter

As the opentelemetry-jaeger crate will be removed in the next major release, these tests can be ignored for the time being to alleviate the issue.

Changes

Ignores tests:
exporter::config::collector::http_client::collector_client_tests::test_bring_your_own_client
exporter::config::collector::tests::test_collector_exporter

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (87153d3) 62.8% compared to head (f6df258) 62.5%.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #1529     +/-   ##
=======================================
- Coverage   62.8%   62.5%   -0.4%     
=======================================
  Files        144     144             
  Lines      19891   19891             
=======================================
- Hits       12502   12433     -69     
- Misses      7389    7458     +69     

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

[TommyCpp]

I think this works.

The issue here is we didn't isolate the env vars between tests. A more robust fix probably is running jaeger tests in single thread.

Maybe we can ignore the jaeger in coverage tests?

[cijothomas]

I think this works.

The issue here is we didn't isolate the env vars between tests. A more robust fix probably is running jaeger tests in single thread.

Maybe we can ignore the jaeger in coverage tests?

yes. I think the easiest approach is to just ignore the tests, and do the jaeger release, followed by its code+tests removal.

[mattbodd]

Thanks @TommyCpp and @cijothomas for your comments. As Cijo mentioned, since we are deprecating opentelemetry-jaeger I didn't opt to fix these flaky tests and instead just silenced them so CI doesn't fail. Is there anything I should do differently or can this change be merged?

[TommyCpp]

Let add a comment that says we ignore this because it's flaky and won't fix because jaeger has been deprecated

[mattbodd]

Let add a comment that says we ignore this because it's flaky and won't fix because jaeger has been deprecated

This is a good suggestion. I've left a comment above each ignored test.