-
Notifications
You must be signed in to change notification settings - Fork 1
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
Dev infrastructure #71
Conversation
Pull Request Test Coverage Report for Build 11903713816Details
💛 - Coveralls |
/// Same as [`run_sync()`], but enables a [`tracing`] subscriber that prints the tracing events to stdout, | ||
/// taking options from the environment variable `RUST_LOG` (see [`mod@tracing_subscriber::fmt`] for details). | ||
#[allow(clippy::type_complexity)] | ||
pub fn run_sync_with_tracing<EP, SP>( |
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.
What is the point of actually providing two flavours of this? Like, why can't we have only run_sync
(and make it use tracing)?
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 basic run_sync
is used for benchmarks. With test-log
I guess we don't need to provide a special function anymore.
048f007
to
59aec37
Compare
Stacked on top of #68
ExecutionResult
andrun_sync_with_tracing()
, to remove some boilerplate from teststesting
module and feature todev
to avoid confusion withtest