You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If cargo config get gets stabilized, we'll be able to circumvent the issue, but in the meantime we do not want to re-implement cargo config parsing in cargo codspeed for something that already has a workaround
Activity
GuillaumeLagrange commentedon Jul 9, 2026
Hello!
Unfurtunately, this is a limitation of cargo that we highlight here: https://codspeed.io/docs/benchmarks/rust/index#cargo-codspeed
As of today, we do not support build.rustflags in cargo config.
However, you can use [target.'cfg(all())'] instead of [build] as a workaround which does the same and is compatible.
Until rust-lang/cargo#5376 is solved, there's not much more than we can do!
If
cargo config getgets stabilized, we'll be able to circumvent the issue, but in the meantime we do not want to re-implement cargo config parsing in cargo codspeed for something that already has a workaround