diff options
| author | bors <bors@rust-lang.org> | 2020-09-13 07:21:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-09-13 07:21:31 +0000 |
| commit | 4e48010b95ed1021677420a9c74d8fed2ce424d4 (patch) | |
| tree | 19772ae7c0cc277d07927927b4e806159f361470 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs | |
| parent | dd33766e4a9a918058c3447d42491e874e21f7cc (diff) | |
| parent | 0be66d7f30ba31638e14c00bd2303dd0327964f4 (diff) | |
| download | rust-4e48010b95ed1021677420a9c74d8fed2ce424d4.tar.gz rust-4e48010b95ed1021677420a9c74d8fed2ce424d4.zip | |
Auto merge of #76588 - guswynn:debug_logging, r=jyn514,Mark-Simulacrum
Add a dedicated debug-logging option to config.toml `@Mark-Simulacrum` and I were talking in zulip and we found that turning on debug/trace logging in rustc is fairly confusing, as it effectively depends on debug-assertions and is not documented as such. `@Mark-Simulacrum` mentioned that we should probably have a separate option for logging anyways. this diff adds that, having the option follow debug-assertions (so everyone's existing config.toml should be fine) and if the option is false to test I ran ./x.py test <something> twice, once with `debug-logging = false` and once with `debug-logging = true` and made sure i only saw trace's when it was true
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions