about summary refs log tree commit diff
path: root/compiler/rustc_mir_transform/src/coverage/graph.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-07-27 23:33:00 +0000
committerbors <bors@rust-lang.org>2023-07-27 23:33:00 +0000
commit6cacb5247fbb5c38f06c1ad71262b0c4eb91a84d (patch)
tree47f0ef122c22fea6d2457fcc715352163629b765 /compiler/rustc_mir_transform/src/coverage/graph.rs
parent500647fd8138cc09e87edb08d62f81654fbf6ef8 (diff)
parent075a6bbef960a7be4cebc6f6b9b7a3d6212f56a6 (diff)
downloadrust-6cacb5247fbb5c38f06c1ad71262b0c4eb91a84d.tar.gz
rust-6cacb5247fbb5c38f06c1ad71262b0c4eb91a84d.zip
Auto merge of #108980 - Enselic:println-and-broken-pipe, r=workingjubilee
Regression test `println!()` panic message on `ErrorKind::BrokenPipe`

No existing test (that I could find) failed if the `panic!()` of the `println!()` family of functions was removed, or if its message was changed:

https://github.com/rust-lang/rust/blob/104f4300cfddbd956e32820ef202a732f06ec848/library/std/src/io/stdio.rs#L1007-L1009

So add such a test.

This is in preparation of adding a hint about the existence of [`unix_sigpipe`](https://github.com/rust-lang/rust/issues/97889) if that is the reason for the panic.

Even if we don't end up adding a hint, this is still a sensible test to have, I think.

`@rustbot` label +A-testsuite +A-io +T-libs +O-unix
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/graph.rs')
0 files changed, 0 insertions, 0 deletions