Add tracing-subscriber

[patrickelectric]

No description provided.

[RaulTrombin]

@patrickelectric what if we put

use tracing::info;
and
tracing_subscriber::fmt().init();

as optional features on common args? examples/common/mod.rs

then users can optionally use as:
cargo run --example ping_1d -- --serial-port /dev/ttyUSB0 ** --is-tracing **

[RaulTrombin]

CI 2 fixed, CI 1 should be OK.

[patrickelectric]

@patrickelectric what if we put

use tracing::info; and tracing_subscriber::fmt().init();

as optional features on common args? examples/common/mod.rs

then users can optionally use as: cargo run --example ping_1d -- --serial-port /dev/ttyUSB0 ** --is-tracing **

Tracing configuration is done via RUST_LOG

[RaulTrombin]

I mean the usage to be optional, with default false, check current CI output. Currently it spam any newcomer user with debugging info, it even increased all tests time from 2s to timeout 30s.

I'm suggesting to pass and aditional clap argument like:
matches.get_flag("enable-tracing") {
tracing_subscriber::fmt().init();
}
On the common module that is shared to all examples.

[patrickelectric]

@RaulTrombin fixed to use env configuration

[patrickelectric]

@RaulTrombin it appears that is an issue with the CI inner script

/etc/github_runner/run-tests.sh: line 17: 1744812078.382779361: syntax error: invalid arithmetic operator (error token is ".382779361")

It's not related to this PR

[RaulTrombin]

@RaulTrombin it appears that is an issue with the CI inner script

/etc/github_runner/run-tests.sh: line 17: 1744812078.382779361: syntax error: invalid arithmetic operator (error token is ".382779361")

It's not related to this PR

it was something on hardware, a power cycle on ping1d fixed.