Checking messages don't have the source

[epage]

cargo

    p.cargo("fix --allow-no-vcs -p foo -p bar")
        .env("__CARGO_FIX_YOLO", "1")
        .with_stdout_data("")
        .with_stderr_data(
            str![[r#"
[CHECKING] bar v0.1.0 ([ROOT]/foo/bar)
[FIXED] bar/src/lib.rs (1 fix)
[CHECKING] foo v0.1.0 ([ROOT]/foo)
[FIXED] src/lib.rs (1 fix)
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s

"#]]
            .unordered(),
        )
        .run();

this

    p.cargo_("fix --allow-no-vcs -p foo -p bar")
        .env("__CARGO_FIX_YOLO", "1")
        .with_stdout_data("")
        .with_stderr_data(
            str![[r#"
[CHECKING] bar v0.1.0
[FIXED] bar/src/lib.rs (1 fix)
[CHECKING] foo v0.1.0
[FIXED] src/lib.rs (1 fix)

"#]]
            .unordered(),
        )
        .run();

[epage]

Blocked on depending on cargo because I'm assuming we'll need some of Cargo's facilities for this

[Pyr0de]

Could we display the manifest_path after removing "Cargo.toml" that we get in the compiler_artifact message?

[epage]

That could be a workaround for path dependencies. For registry dependencies, cargo shows nothing. For git dependencies, it likely shows something else.