2c1af52ace
This branch makes the following changes to the CI test workflows: - Consolidate all tests into a single workflow again. We had previously broken things out to allow restarting only some failed checks, but now GitHub Actions allows restarting individual jobs, which is much nicer, and we can combine everything into one workflow. - Gate starting any tests/checks on an initial `cargo check` run. This should mean that if code doesn't compile, we don't spin up a huge number of test jobs that all end up failing, and delaying other PRs' CI runs. - Use `cargo nextest` for running tests. This should make test runs a bit quicker, and also get us other nice features like retries for flaky tests. - Switch to `taiki-e/install-action` for installing stuff like `cargo-hack`, `nextest`, and `wasm-pack`. This is a bit nicer than just `curl`ing stuff. - Use a matrix for testing across toolchains/OSes, instead of having separate jobs. This reduces the complexity of the CI workflow a bit. Signed-off-by: Eliza Weisman <eliza@buoyant.io>
tracing-futures
Utilities for instrumenting futures-based code with tracing.
Overview
tracing is a framework for instrumenting Rust programs to collect
structured, event-based diagnostic information. This crate provides utilities
for using tracing to instrument asynchronous code written using futures and
async/await.
The crate provides the following traits:
-
Instrumentallows atracingspan to be attached to a future, sink, stream, or executor. -
WithSubscriberallows atracingSubscriberto be attached to a future, sink, stream, or executor.
Compiler support: requires rustc 1.49+
Supported Rust Versions
Tracing is built against the latest stable release. The minimum supported version is 1.49. The current Tracing version is not guaranteed to build on Rust versions earlier than the minimum supported version.
Tracing follows the same compiler support policies as the rest of the Tokio project. The current stable Rust compiler and the three most recent minor versions before it will always be supported. For example, if the current stable compiler version is 1.45, the minimum supported version will not be increased past 1.42, three minor versions prior. Increasing the minimum supported compiler version is not considered a semver breaking change as long as doing so complies with this policy.
License
This project is licensed under the MIT license.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tracing by you, shall be licensed as MIT, without any additional terms or conditions.