-
Notifications
You must be signed in to change notification settings - Fork 19
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
fix(test): concurrent access to global OTEL configuration. #1097
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1097 +/- ##
==========================================
+ Coverage 57.52% 60.63% +3.11%
==========================================
Files 18 18
Lines 1189 1189
==========================================
+ Hits 684 721 +37
+ Misses 505 468 -37
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
3940a2e
to
a1058c5
Compare
acff66f
to
a51beff
Compare
- name: Run integration-tests coverage | ||
run: make integration-tests |
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've also took this opportunity to remove the deprecated actions-rc/cargo
action.
The OTEL test is flaky because it relies on the global OTEL configuration that can be overwrite by other concurrent tests. Therefore, the OTEL test now is behind a feature gate to ensure that it will be run on isolation. Signed-off-by: José Guilherme Vanz <[email protected]>
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.
Thanks!
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.
nice fixes!
Description
The OTEL test is flaky because it relies on the global OTEL configuration that can be overwrite by other concurrent tests.
Therefore, the OTEL test now is behind a feature gate to ensure that it will be run on isolation.
Fix #916