Output

Why the output looks like this: About QuickRust’s build output.

Line forms

Everything QuickRust writes for people is ASCII.

A message is a head, then its details after : , separated by , ; a duration, when there is one, closes the line in square brackets. A tag with nothing to add stands alone: OK, or OK [0.42s] when only the time is worth saying.

Of an outcome line only the tag is coloured. The status line and detail lines such as Locked ... are dim; the words of dependency lines are coloured (below). There is no colour when NO_COLOR is set (not empty) or CARGO_TERM_COLOR=never, and when the line does not go to a terminal, unless CARGO_TERM_COLOR=always. Without colour the tag carries the meaning.

Durations are shown as 120ms, 4.21s, 2m05.3s; sizes as 942 B, 281.0 KiB, 5.6 MiB.

When QuickRust presents the output

QuickRust presents a command’s output when all of these hold:

• output = "qrust" (the default in fast mode; in compat mode only when set explicitly);
• stderr is a terminal;
• the command is not a Cargo alias;
• the command line has none of --message-format, -v, -vv, --verbose, -q, --quiet, --color (before any --).

Otherwise Cargo’s output reaches the terminal, pipe or file unchanged. Per command:

For a presented command QuickRust asks Cargo for its JSON messages (builds) and its progress, and asks it to draw in ASCII (term.unicode = false, so cargo tree draws |-- and `--). These go to that one Cargo as --config arguments; build scripts, nested Cargo and the programs a command runs do not see them.

Builds

Status line

One line, redrawn in place, indented to the message column:

     Building [=========>          ] 112/240, 98 compiled, 14 fresh; tokio, syn
     Downloading [=====>              ] 7/25 crates, 2.1 MiB left
     Updating crates.io index: 26 packages looked up
     Waiting for the lock on the package cache (another Cargo holds it)

The bar is 20 cells wide. The line is cut to the terminal’s width with .... It is removed before the summary.

Lines above the status line

| Line | Example | |—|—| | A compiler error: the crate in red, then rustc’s rendering, in full, as it arrives | --- app (bin) followed by error[E0425]: cannot find function ... | | Downloads, when done | ` Downloaded 1 crate, 4.4 KiB [0.32s] | | Lockfile changes | Locked 1 package to highest compatible version | | Lines QuickRust does not recognise (build script failures, cargo:warning=` output, resolution errors) | as Cargo printed them |

Warnings are not printed as they arrive; they are counted.

Summary

Each unit is counted once: compiled (rustc ran), fresh (Cargo found it up to date) or restored from QuickRust's cache. Counts that are zero are left out. Warnings follow the summary in one line, the three most frequent lints first:

WARN 23 warnings in app and util: unused_variables x17, dead_code x4, +2 more; `qrust warnings` shows them

run, test, bench

After the build summary the command itself runs and finds everything fresh. Cargo’s “Finished” and “Running” lines of cargo run are not shown, nor are warnings Cargo would replay. The program’s output is not touched.

For test and bench, QuickRust shows Cargo’s lines its way and closes with the counts of every test program added up:

OK   Built: 1 compiled, 1 fresh [0.42s]
     unittests src/lib.rs
running 132 tests
...
test result: ok. 132 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out; finished in 0.31s
     doc-tests app
...
OK   Tests: 140 passed, 2 ignored [1.12s]

On Windows the test run’s lines are Cargo’s.

Commands that do not build

     updated    serde                    1.0.209 -> 1.0.210
     added      hashbrown                0.15.0
     removed    autocfg                  1.3.0
OK   Lockfile updated: 1 updated, 1 added, 1 removed [0.92s]

The closing line:

QuickRust’s own commands

Examples:

OK   Rust 1.99.0 ready (1.99.0-x86_64-unknown-linux-gnu) [38.20s]
OK   Installed hello 0.3.0: hello -> ~/.qrust/bin [12.41s]
OK   Freed 1.2 GiB: QuickRust's cache 9.8 GiB -> 8.6 GiB (at most 10.0 GiB; keeps 2.0 GiB of the disk free, 40.1 GiB free now) [0.84s]
FAIL toolchain no-such-toolchain-xyz (from `+toolchain` argument): no toolchain is named `no-such-toolchain-xyz` (`qrust toolchain link no-such-toolchain-xyz <dir>` names one)

Stored output

For every build QuickRust presented, every line Cargo and rustc wrote (at most 200,000 per run) is stored with the run, in cargo-output.jsonl in the run’s event directory. Status-line redraws are not stored. A run found up to date holds the stored output of the build it is up to date with, whose warnings its WARN line repeats. qrust warnings, qrust errors and qrust log print it again (Commands). The stored output is kept as long as the run’s raw events (measurement.keep-raw-events). Commands that do not build are not stored.