Expand description
Shared helpers for the integration-test suites of the consumer crates.
Backtrace and spantrace snapshots are platform- and toolchain-specific, so each snapshot is blessed and asserted only on the toolchain that produced it; the variance lives in the snapshot filename (channel + target triple) rather than in a cross-toolchain normalization battery. The filters here are therefore deliberately light: they only erase build-to-build noise (compilation hashes, line/column numbers, machine-specific paths).
Modules§
- settings
instasnapshot redaction profiles that erase build-to-build noise (compilation hashes, line/column numbers, machine-specific paths) from backtrace and spantrace snapshots.
Constants§
- CHANNEL
- The toolchain channel (
stableorunstable) embedded in snapshot file names so toolchain-specific snapshots stay in separate files.
Functions§
- force_
backtrace - Force backtrace capture on the current thread so snapshots are deterministic
regardless of the ambient
RUST_BACKTRACEenvironment. - init_
test_ subscriber - Install a test subscriber with an
ErrorLayerso span traces are captured for the duration of the returned guard. - init_
test_ subscriber_ without_ error_ layer - Install a test subscriber without an
ErrorLayer, so captured span traces reportUnsupported— distinct from the no-subscriberEmptycase — for the duration of the returned guard.