Update tracing to 0.1.25

[tmiasko]

• Update tracing from 0.1.18 to 0.1.25
• Update tracing-subscriber from 0.2.13 to 0.2.16
• Update tracing-tree from 0.1.6 to 0.1.8
• Add pin-project-lite to the list of allowed dependencies (it is now a direct dependency of tracing).

[rust-highfive]

r? @Mark-Simulacrum

(rust-highfive has picked a reviewer for you, use r? to override)

[tmiasko]

Added pin-project-lite, which is now a direct dependency of tracing, to the list of allowed dependencies

[bors]

☔ The latest upstream changes (presumably #82611) made this pull request unmergeable. Please resolve the merge conflicts.

[Mark-Simulacrum]

Could you provide a link to the changelogs and some particular rationale for this update (beyond just keeping things up to date)?

[tmiasko]

The release notes can be found at:

• https://github.com/tokio-rs/tracing/releases
• https://github.com/davidbarsky/tracing-tree/releases

I was originally motivated by slight reduction in a code generated for statically disabled instrumentation, although I don't see it explicitly mentioned in release notes for that version. The rest is indeed just to keep things up-to date.

@rustbot label: +S-waiting-on-review

[Mark-Simulacrum]

I've done the digging now, but it would've been great to provide the changelog in a more directed fashion - e.g., links to each release - if the upstream crate doesn't maintain a changelog file.

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 2abe7c8 with merge f2c6646afcc0b532fc328d7fa18c47749d8d9610...

[bors]

☀️ Try build successful - checks-actions
Build commit: f2c6646afcc0b532fc328d7fa18c47749d8d9610 (f2c6646afcc0b532fc328d7fa18c47749d8d9610)

[rust-timer]

Queued f2c6646afcc0b532fc328d7fa18c47749d8d9610 with parent 939b143, future comparison URL.

[rust-timer]

Finished benchmarking try commit (f2c6646afcc0b532fc328d7fa18c47749d8d9610): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

[Mark-Simulacrum]

Seems to be a mild improvement overall, though potentially a regression in compile times (hard to say if noise or not). @bors r+

[bors]

📌 Commit 2abe7c8 has been approved by Mark-Simulacrum

[bors]

⌛ Testing commit 2abe7c8 with merge 476acbf...

[bors]

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 476acbf to master...