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
Adjust tracing configuration to follow the POM model #3570
Conversation
b216ac0
to
1b43f53
Compare
9fa4b79
to
526f458
Compare
526f458
to
37b0656
Compare
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.
Very nice, I just would like to request to keep some of the traces on by default (as it was introduced in the commit: 0525536).
configure the tracers using the POM model Implement defaultPartialTraceConfiguration
daf816c
to
e879f82
Compare
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.
LGTM
e879f82
to
73cb247
Compare
bors r+ |
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.
The new tracing system is not intended to be toggle-able on a per-tracer basis.
So while it's a cleanup, it's a little misleading -- the config tracer toggles will have no effect, at least for now.
In future, we might still resort to it, but that's not the current intention.
Build failed: |
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.
Probably want to squash this down.
263fabd
to
944144a
Compare
All the tests appear to fail in the same way:
|
977cb41
to
000a51f
Compare
bors r+ |
Build failed: |
000a51f
to
0995966
Compare
0995966
to
bdfd5ae
Compare
bors merge |
Build succeeded: |
Resolves #3534