Tracing update

[Mark-Simulacrum]

This does not bring the more significant changes that are coming down the pipeline, but since I've already prepared the PR leaving it up :)

See #76210 (comment):

Unfortunately, tracing 0.1.20 — which contained the change to reduce the amount of code generated by the tracing macros — had to be yanked, as it broke previously-compiling code for some downstream crates. I've not yet had the chance to fix this and release a new patch. So, in order to benefit from the changes to reduce generated code, you'll need to wait until there's a new version of tracing as well as tracing-attributes and tracing-core.

[Mark-Simulacrum]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion

[bors]

⌛ Trying commit 77d4f94 with merge f675271e5c4ae4c4919a22775104a2ead9ff53d8...

[hawkw]

👋 Unfortunately, tracing 0.1.20 — which contained the change to reduce the amount of code generated by the tracing macros — had to be yanked, as it broke previously-compiling code for some downstream crates. I've not yet had the chance to fix this and release a new patch. So, in order to benefit from the changes to reduce generated code, you'll need to wait until there's a new version of tracing as well as tracing-attributes and tracing-core.

But, you're still getting some minor fixes etc, so it's probably good to update regardless.

[bors]

☀️ Try build successful - checks-actions, checks-azure
Build commit: f675271e5c4ae4c4919a22775104a2ead9ff53d8 (f675271e5c4ae4c4919a22775104a2ead9ff53d8)

[rust-timer]

Queued f675271e5c4ae4c4919a22775104a2ead9ff53d8 with parent 58d5ce4, future comparison URL.

[hawkw]

FWIW i would not really expect any significant performance difference from these updates, since the macro change isn't included.

[rust-timer]

Finished benchmarking try commit (f675271e5c4ae4c4919a22775104a2ead9ff53d8): 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

[Mark-Simulacrum]

Maybe a tiny win (~0.1%). r? @oli-obk

[oli-obk]

@bors r+

[bors]

📌 Commit 77d4f94 has been approved by oli-obk

[bors]

⌛ Testing commit 77d4f94 with merge faa5291f1e7b25ba498873e1ff37c0688edcd4db...

[bors]

💔 Test failed - checks-actions

[jyn514]

#76442

\rustdoc-ui\failed-doctest-output.rs
diff of stdout:

1	
2	running 2 tests
-	test $DIR/failed-doctest-output.rs - OtherStruct (line 21) ... FAILED
4	test $DIR/failed-doctest-output.rs - SomeStruct (line 11) ... FAILED
+	test $DIR/failed-doctest-output.rs - OtherStruct (line 21) ... FAILED

@bors retry

[bors]

⌛ Testing commit 77d4f94 with merge fa79db8...

[bors]

☀️ Test successful - checks-actions, checks-azure
Approved by: oli-obk
Pushing fa79db8 to master...