more: test output often looks messy and input is no longer shown afterwards #6100
Description
Often, when running cargo test --features "more" --no-default-features the output looks messy:
[snipped]
test test_more::test_argument_from_file ... ok
test test_more::test_more_error_on_single_arg ... ok
test test_more::test_invalid_arg ... ok
test test_more::test_more_error_on_multiple_files ... ok
test test_more::test_more_no_arg ... ok
test test_more::test_more_invalid_file_perms ... ok
test test_more::test_more_pattern_found ... ok
test test_more::test_more_pattern_not_found ... ok
test common::random::tests::test_generate_random_strings_when_length_is_around_critical_buffer_sizes ... ok
test test_more::test_valid_arg ... ok
test result: ok. 37 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.07s
In most such cases, the input in the console (using bash) is no longer shown afterwards and has to be reset with stty sane.