about summary refs log tree commit diff
path: root/compiler/rustc_interface/src
diff options
context:
space:
mode:
authorMatthias Krüger <476013+matthiaskrgr@users.noreply.github.com>2025-06-30 20:49:42 +0200
committerGitHub <noreply@github.com>2025-06-30 20:49:42 +0200
commitd3c02b48df5c0ae8a447168589605e6a6c6daabc (patch)
tree1bed7056185289c922c2b8f54eebd9ce294b0a99 /compiler/rustc_interface/src
parent1be0c62069375f346c50788f3a7bc7a14337cdfe (diff)
parent0cb0b22bf209aec2e64fbd6eec9258f88b8e7154 (diff)
downloadrust-d3c02b48df5c0ae8a447168589605e6a6c6daabc.tar.gz
rust-d3c02b48df5c0ae8a447168589605e6a6c6daabc.zip
Rollup merge of #143180 - jieyouxu:forest, r=Kobzol
Use `tracing-forest` instead of `tracing-tree` for bootstrap tracing

I find the `tracing-forest` output easier to comprehend.

Note that this is not a strict improvement -- `tracing-forest` output contains some emojis and redundant log levels, but customizing it seems to be... non-trivial. Despite this, I still find `tracing-forest` easier to follow than `tracing-tree`, even when I tried to tune `tracing-tree` output.

### Preview

```bash
BOOTSTRAP_TRACING=debug ./x test library/std --dry-run
```

With `tracing-forest` (this PR), it looks like

![Screenshot 2025-06-29 174802](https://github.com/user-attachments/assets/1ab9150f-48f8-4fb3-b004-27bcf8bbc0f5)

With `tracing-tree` (before this PR), it looked like

![Screenshot 2025-06-29 175227](https://github.com/user-attachments/assets/659e254d-15ab-47dd-af11-98e2331d4d7a)

r? `@Kobzol`
Diffstat (limited to 'compiler/rustc_interface/src')
0 files changed, 0 insertions, 0 deletions