Fix some minor formatting issues.

This commit is contained in:
Eric Huss 2021-03-05 14:01:01 -08:00
parent f03d47ce4b
commit 9ea3503680
2 changed files with 5 additions and 4 deletions

View File

@ -44,8 +44,8 @@ pub fn exec(config: &mut Config, args: &ArgMatches<'_>) -> CliResult {
let id = args.value_of("id").unwrap();
if id != on_disk_report.id {
return Err(anyhow!(
"Expected an id of `{}`, but `{}` was provided on the command line.\
Your report may have been overwritten by a different one.",
"Expected an id of `{}`, but `{}` was provided on the command line. \
Your report may have been overwritten by a different one.",
on_disk_report.id,
id
)

View File

@ -1,4 +1,5 @@
/// Tests for future-incompat-report messages
//! Tests for future-incompat-report messages
use cargo_test_support::registry::Package;
use cargo_test_support::{basic_manifest, is_nightly, project};
@ -139,7 +140,7 @@ fn test_multi_crate() {
.unwrap();
// Extract the 'id' from the stdout. We are looking
// for the id in a line of the form "run `cargo describe-future-incompatibilities --id 721d0666-81b6-4765-84fc-fd2832328324`"
// for the id in a line of the form "run `cargo describe-future-incompatibilities --id yZ7S`"
// which is generated by Cargo to tell the user what command to run
// This is just to test that passing the id suppresses the warning mesasge. Any users needing
// access to the report from a shell script should use the `--future-incompat-report` flag