Skip to content

benchmark runner is passed --bench even when harness = false #3027

@bluss

Description

@bluss

I'm experimenting with benchmarking for Rust stable. One way to tie into cargo is simply to use the benchmark facility:

[[bench]]
name = "benchmarks"
harness = false

This compiles and runs, using a dev-dependency in the benchmark runner and so on. The only unexpected part is that it is passed --bench as a command line argument (and to add to that, it's not the first argument but the last). I'd expect it does not use --bench when harness = false.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: bugCommand-benchS-propose-closeStatus: A team member has nominated this for closing, pending further input from the team

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions