Skip to content

Add an easy way to check the error message #398

@madsmtm

Description

@madsmtm

In rust-lang/rust#147967, I and several others were confused by a bisection because the compiler changed in other ways in the regression range that also broke building the repository.

I know that we could have avoided that with something like:

#!/bin/sh
cargo check 2>&1 | grep "message"
$ cargo bisect-rustc --script=./test.sh

But that's a bit of a mouthful. Do you think it would be worthwhile to add a --message parameter to make this easier?


Alternatively, or maybe additionally, cargo-bisect-rustc could by default parse the error message(s) from the end bisection, and ensure that it stays the same across all the "inner" invocations. Or at least that it warns if they changed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions