diff options
author | Son <leson.phung@gmail.com> | 2019-03-26 09:19:20 +1100 |
---|---|---|
committer | Eliza Weisman <eliza@buoyant.io> | 2019-03-25 15:19:20 -0700 |
commit | 1524ee4b60792c7046748ebc4a9db2e687b971d3 (patch) | |
tree | 3c00e3281dec77d8abab3f14bc63d2368ff9fbfc /azure-pipelines.yml | |
parent | 7793d637397a0e73096a1df31c777920545e9d1e (diff) |
trace: Add static level filtering (#987)
## Motivation
`tokio-trace` should have static verbosity level filtering, like the
`log` crate. The static max verbosity level should be controlled at
compile time with a set of features. It should be possible to set a
separate max level for release and debug mode builds.
## Solution
We can do this fairly similarly to how the `log` crate does it:
`tokio-trace` should export a constant whose value is set based on the
static max level feature flags. Then, we add an if statement to the
`span!` and `event!` macros which tests if that event or span's level
is enabled.
Closes #959
Diffstat (limited to 'azure-pipelines.yml')
-rw-r--r-- | azure-pipelines.yml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/azure-pipelines.yml b/azure-pipelines.yml index 57f47e68..4170b017 100644 --- a/azure-pipelines.yml +++ b/azure-pipelines.yml @@ -47,6 +47,7 @@ jobs: - tokio-timer - tokio-trace - tokio-trace/tokio-trace-core + - tokio-trace/test_static_max_level_features - template: ci/azure-cargo-check.yml parameters: |