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
> **Note**: This may not work on all targets since `cargo-bisect-rustc` doesn't properly handle rustup manifests, which alias some targets to other targets.
You can add custom messages when bisecting a regression. Taking inspiration from git-bisect, with `term-new` and `term-old` you can set custom messages to indicate if a regression matches the condition set by the bisection.
144
144
@@ -151,18 +151,8 @@ cargo bisect-rustc \
151
151
--term-new "Yes, this build reproduces the regression, compile error"
152
152
```
153
153
154
-
Note that `--term-{old,new}` are aware of the `--regress` parameter. If the bisection is looking for a build to reproduce a regression (i.e.`--regress {error,ice}`), `--term-old` indicates a point in time where the regression does not reproduce and `--term-new` indicates that it does.
154
+
In other words, `--term-old`is displayed for older compilers that **do not** exhibit the regression.`--term-new` is for newer compilers which do exhibit the regression.
155
155
156
-
On the other hand, if `--regress {non-error,non-ice,success}` you are looking into bisecting when a condition of error stopped being reproducible (e.g. some faulty code does not produce an error anymore). In this case `cargo-bisect` flips the meaning of these two parameters.
156
+
What counts as a "regression" is defined by the [`--regress`](usage.html#regression-check) CLI option. By default, a regression is a compile-error (which is equivalent to `--term-new`). If you flip the definition of a "regression" with `--regress=success`, then a regression is a successful compile (which is *also* equivalent to `--term-new`).
157
157
158
-
Example:
159
-
```sh
160
-
cargo bisect-rustc \
161
-
--start=2018-08-14 \
162
-
--end=2018-10-11 \
163
-
--regress=success \
164
-
--term-old "This build does not compile" \
165
-
--term-new "This build compiles"
166
-
```
167
-
168
-
See [`--regress`](usage.html#regression-check) for more details.
158
+
There are default terms based on the current `--regress` setting. Customizing the terms is most useful when using [scripting](#testing-with-a-script). For example, in the [Documentation changes](examples/doc-change.md) example, the customized terms can more clearly express the results of the script of whether or not it found what it was looking for in the documentation.
0 commit comments