This is likely related to a similar issue in Tokio tokio-rs/tokio#6910. A comment from Alex Crichton suggests that until a fix is available for wasm-bindgen, we can
either pin Rust to 1.81 or update Node to 20.x on the CI runners.
In Tokio, the wasm tests have been pinned to Rust 1.81.0 for the time being, a similar approach is probably a good mitigation here.
Version
tracing master branch
Rust 1.82.0
Platform
Crates
tracing
Description
It's only the tests in the tracing crate that fail, the other crates' tests all pass fine.
The first test to fail is tests/collector.rs, but that may just be the first test that can run under wasm.
Bug Report
The
tracing
crate tests are failing when being run on wasm since Rust 1.82.0.For example: https://github.com/tokio-rs/tracing/actions/runs/11579459399/job/32235756245?pr=3122
This is likely related to a similar issue in Tokio tokio-rs/tokio#6910. A comment from Alex Crichton suggests that until a fix is available for
wasm-bindgen
, we can either pin Rust to 1.81 or update Node to 20.x on the CI runners.In Tokio, the wasm tests have been pinned to Rust 1.81.0 for the time being, a similar approach is probably a good mitigation here.
Version
master
branchPlatform
Crates
tracing
Description
It's only the tests in the
tracing
crate that fail, the other crates' tests all pass fine.The first test to fail is
tests/collector.rs
, but that may just be the first test that can run under wasm.The output is (taken from the PR 3122 link above: