|
1 |
| -Usage: cargo <COMMAND> |
| 1 | +Bisects rustc toolchains with rustup |
2 | 2 |
|
3 |
| -Commands: |
4 |
| - bisect-rustc Bisects rustc toolchains with rustup |
5 |
| - help Print this message or the help of the given subcommand(s) |
| 3 | +Usage: cargo bisect-rustc [OPTIONS] [-- <COMMAND_ARGS>...] |
| 4 | + |
| 5 | +Arguments: |
| 6 | + [COMMAND_ARGS]... |
| 7 | + Arguments to pass to cargo or the file specified by --script during tests |
6 | 8 |
|
7 | 9 | Options:
|
8 |
| - -h, --help Print help |
| 10 | + -a, --alt |
| 11 | + Download the alt build instead of normal build |
| 12 | + |
| 13 | + --access <ACCESS> |
| 14 | + How to access Rust git repository |
| 15 | + |
| 16 | + [default: github] |
| 17 | + [possible values: checkout, github] |
| 18 | + |
| 19 | + --by-commit |
| 20 | + Bisect via commit artifacts |
| 21 | + |
| 22 | + -c, --component <COMPONENTS> |
| 23 | + additional components to install |
| 24 | + |
| 25 | + --end <END> |
| 26 | + Right bound for search (*with* regression). You can use a date (YYYY-MM-DD), git tag name |
| 27 | + (e.g. 1.58.0) or git commit SHA. |
| 28 | + |
| 29 | + --force-install |
| 30 | + Force installation over existing artifacts |
| 31 | + |
| 32 | + -h, --help |
| 33 | + Print help (see a summary with '-h') |
| 34 | + |
| 35 | + --host <HOST> |
| 36 | + Host triple for the compiler |
| 37 | + |
| 38 | + [default: [..]] |
| 39 | + |
| 40 | + --install <INSTALL> |
| 41 | + Install the given artifact |
| 42 | + |
| 43 | + --preserve |
| 44 | + Preserve the downloaded artifacts |
| 45 | + |
| 46 | + --preserve-target |
| 47 | + Preserve the target directory used for builds |
| 48 | + |
| 49 | + --prompt |
| 50 | + Manually evaluate for regression with prompts |
| 51 | + |
| 52 | + --regress <REGRESS> |
| 53 | + Custom regression definition |
| 54 | + |
| 55 | + [default: error] |
| 56 | + |
| 57 | + Possible values: |
| 58 | + - error: Marks test outcome as `Regressed` if and only if the `rustc` process reports |
| 59 | + a non-success status. This corresponds to when `rustc` has an internal compiler error |
| 60 | + (ICE) or when it detects an error in the input program. This covers the most common use |
| 61 | + case for `cargo-bisect-rustc` and is thus the default setting |
| 62 | + - success: Marks test outcome as `Regressed` if and only if the `rustc` process reports |
| 63 | + a success status. This corresponds to when `rustc` believes it has successfully compiled |
| 64 | + the program. This covers the use case for when you want to bisect to see when a bug was |
| 65 | + fixed |
| 66 | + - ice: Marks test outcome as `Regressed` if and only if the `rustc` process issues a |
| 67 | + diagnostic indicating that an internal compiler error (ICE) occurred. This covers the |
| 68 | + use case for when you want to bisect to see when an ICE was introduced on a codebase |
| 69 | + that is meant to produce a clean error |
| 70 | + - non-ice: Marks test outcome as `Regressed` if and only if the `rustc` process does not |
| 71 | + issue a diagnostic indicating that an internal compiler error (ICE) occurred. This |
| 72 | + covers the use case for when you want to bisect to see when an ICE was fixed |
| 73 | + - non-error: Marks test outcome as `Baseline` if and only if the `rustc` process reports |
| 74 | + error status and does not issue any diagnostic indicating that an internal compiler |
| 75 | + error (ICE) occurred. This is the use case if the regression is a case where an |
| 76 | + ill-formed program has stopped being properly rejected by the compiler. (The main |
| 77 | + difference between this case and `success` is the handling of ICE: `success` assumes |
| 78 | + that ICE should be considered baseline; `non-error` assumes ICE should be considered a |
| 79 | + sign of a regression.) |
| 80 | + |
| 81 | + --script <SCRIPT> |
| 82 | + Script replacement for `cargo build` command |
| 83 | + |
| 84 | + --start <START> |
| 85 | + Left bound for search (*without* regression). You can use a date (YYYY-MM-DD), git tag |
| 86 | + name (e.g. 1.58.0) or git commit SHA. |
| 87 | + |
| 88 | + -t, --timeout <TIMEOUT> |
| 89 | + Assume failure after specified number of seconds (for bisecting hangs) |
| 90 | + |
| 91 | + --target <TARGET> |
| 92 | + Cross-compilation target platform |
| 93 | + |
| 94 | + --term-new <TERM_NEW> |
| 95 | + Text shown when a test does match the condition requested |
| 96 | + |
| 97 | + --term-old <TERM_OLD> |
| 98 | + Text shown when a test fails to match the condition requested |
| 99 | + |
| 100 | + --test-dir <TEST_DIR> |
| 101 | + Root directory for tests |
| 102 | + |
| 103 | + [default: .] |
| 104 | + |
| 105 | + -v, --verbose... |
| 106 | + |
| 107 | + |
| 108 | + -V, --version |
| 109 | + Print version |
| 110 | + |
| 111 | + --with-dev |
| 112 | + Download rustc-dev [default: no download] |
| 113 | + |
| 114 | + --with-src |
| 115 | + Download rust-src [default: no download] |
| 116 | + |
| 117 | + --without-cargo |
| 118 | + Do not install cargo [default: install cargo] |
| 119 | + |
| 120 | +Examples: |
| 121 | + Run a fully automatic nightly bisect doing `cargo check`: |
| 122 | + ``` |
| 123 | + cargo bisect-rustc --start 2018-07-07 --end 2018-07-30 --test-dir ../my_project/ -- check |
| 124 | + ``` |
| 125 | + |
| 126 | + Run a PR-based bisect with manual prompts after each run doing `cargo build`: |
| 127 | + ``` |
| 128 | + cargo bisect-rustc --start 6a1c0637ce44aeea6c60527f4c0e7fb33f2bcd0d / |
| 129 | + --end 866a713258915e6cbb212d135f751a6a8c9e1c0a --test-dir ../my_project/ --prompt -- build |
| 130 | + ``` |
0 commit comments