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
It looks like CLion only supports Rust's built-in test runner. I don't think that it would make sense to filter out the --format=json etc arguments in bootimage because the output format would still be incompatible if CLion expects some specific JSON output.
It's probably also worth mentioning that I'm planning to release a new bootloader version that does no longer require bootimage at all and instead lets user define their own small "runner" crates. This should allow you to adjust your runner exactly as you need, including the QEMU arguments.
Rust plugin uses its test tool window to perform tests. It needs cargo test JSON output to show it there, and adds this flag implicitly on test.
As a workaround, you can make an alias to test command in .cargo/config.toml and avoid Rust plugin to add --format=json to the command. Then, use cargo t in cargo run configuration.
I think bootimage has some problems with the custom test runner on CLion/Rust plugin.
CLion can create a Cargo run configuration for tests. This creates the following cargo command:
Unfortunately, the arguments after
--
are passed to qemu as isRunning the test via
cargo test
works, though.The text was updated successfully, but these errors were encountered: