a global default trace dispatcher has already been set about console

[mrcnski]

I think maybe it happened when an instance of the process crashed and I ran it again. Anyway, if you can't reproduce then feel free to close the issue. 👍🏻

[hds]

@zoechi For integration tests (or any tests that use tracing subscribers), you need to use set_default to set a thread local subscriber.

This is because cargo runs each test from a single integration test file in its own thread, but in the same executable and if each test tries to set a global subscriber they will clash (and panic as you saw).

It sounds like you're also spawning your own threads in your tests, in that case you need to set up a separate subscriber in each thread you create.

(this situation is a bit different from the original issue)

[hds]

@mrcnski Thanks for your error report.

I couldn't reproduce this error with the following minimal project. Could you see if you can modify it to produce the error you see in polkadot?

Cargo.toml:

[package]
name = "console-eyre"
version = "0.1.0"
edition = "2021"

[dependencies]
color-eyre = "0.6.2"
console-subscriber = "0.2.0"
eyre = "0.6.11"

src/main.rs:

fn main() -> eyre::Result<()> {
    console_subscriber::init();
    color_eyre::install()?;

    println!("Hello, world!");

    Ok(())
}

I ran it with:

RUSTFLAGS="--cfg tokio_unstable" cargo run --release

[hds]

Closing this as can't repro at request of original author @mrcnski.

[zoechi]

I just run into this error when I run more than one integration test that invokes production code calling

tracing::subscriber::set_global_default(subscriber);

It was kinda hard to find because the code runs in a thread and the error was masked by another error just before join_handle.join()

[zoechi]

Thanks for the info🚀