-
Notifications
You must be signed in to change notification settings - Fork 46
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
editoast: force 'otel::tracing=info' for some tests #10531
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #10531 +/- ##
=======================================
Coverage 81.90% 81.90%
=======================================
Files 1079 1079
Lines 107473 107487 +14
Branches 734 734
=======================================
+ Hits 88024 88037 +13
- Misses 19409 19410 +1
Partials 40 40
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ works for me a bit better (less logs) than the alternative.
It looks a bit more elegant, but again, not sharp enough on the matter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I like this proposition better.
- Keeping the ability to configure
RUST_LOG
for running tests is useful (to me at least). - Tests that require a specific log directives will be emphasized and show explicitly which directives affects the behavior of the tested feature.
fa48f4c
to
ff2acc0
Compare
Since #10526 has been abandoned in favor of the current PR, let's merge it? |
The STDCM log feature depends on Opentelemetry span being created in the Axum middleware. If `RUST_LOG=warn`, tests will fail because no span is created and therefore no trace ID is created and tests depends on this trace ID. The added directives are applied after reading `RUST_LOG`. Signed-off-by: Jean SIMARD <[email protected]>
ff2acc0
to
9d7bcfc
Compare
Signed-off-by: Jean SIMARD <[email protected]>
9d7bcfc
to
4eeec9f
Compare
The STDCM log feature depends on Opentelemetry span being created in the Axum middleware. If
RUST_LOG=warn
, tests will fail because no span is created and therefore no trace ID is created and tests depends on this trace ID.The added directives are applied after reading
RUST_LOG
.This is an alternative solution to what was proposed in #10526.