Why is this crate built twice when using --profile test?

image


These are the outputs of cargo check --profile test --timings

The exact same version of Tokio with the exact same set of flags is getting compiled twice.
Is this a bug?
In all crates that use tokio I use tokio = { workspace = true } :thinking:

I don't know how to upload files so I uploaded the cargo timing html here lol

This doesn't happen without the --profile test part

What are you doing? You need to provide more information (such as the contents of Cargo.toml and the output of cargo tree).

The file you uploaded has been deleted. You can drag&drop or paste images.

I'm... unfortunately not allowed to do that. I'll be closing this as I won't be able to provide enough information :confused:
Thanks anyways

One possiblility is if you have a proc-macro crate that depends on tokio, proc-macro crates a built slighlty differently because of how they interact with cross-compilation