chore: remove redundant test logging

[scottgerring]

Fixes #2841
Design discussion issue (if applicable) #

Changes

Please provide a brief description of the changes here.

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 ✅

Project coverage is 81.3%. Comparing base (1d9bd25) to head (1f3d7b8).

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #2943     +/-   ##
=======================================
- Coverage   81.3%   81.3%   -0.1%     
=======================================
  Files        126     126             
  Lines      24289   24289             
=======================================
- Hits       19763   19759      -4     
- Misses      4526    4530      +4     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[scottgerring]

Had a quick skim for other instances and didn't find anything. Is it this simple?

[cijothomas]

@scottgerring I compared the CI logs for integration test for this PR vs existing. The logs are not shown, for the CI runs in this PR, but it does show up in other PRs.

What's your thought on removing our custom print-to-stdout, and instead rely on tracing::fmt instead?

[scottgerring]

@scottgerring I compared the CI logs for integration test for this PR vs existing. The logs are not shown, for the CI runs in this PR, but it does show up in other PRs.
🤝

What's your thought on removing our custom print-to-stdout, and instead rely on tracing::fmt instead?

We could certainly do it, although I am apprehensive about adding more stuff that uses tracing within OTel - see e.g. the issue with telemetry suppression you were working on. I know that won't be a problem here, but I don't see so much value in adding it in - the main thing is to get diagnostics out.

Do you have an opinion on it @cijothomas ?