crosvm/gpu_display
David Tolnay b4bd00fdad error: Print errors using Display impl
I have been running into Debug-printed error messages too often and
needing to look up in the source code each level of nested errors to
find out from the comment on the error variant what the short name of
the variant means in human terms. Worse, many errors (like the one shown
below) already had error strings written but were being printed from the
calling code in the less helpful Debug representation anyway.

Before:
    [ERROR:src/main.rs:705] The architecture failed to build the vm: NoVarEmpty

After:
    [ERROR:src/main.rs:705] The architecture failed to build the vm: /var/empty doesn't exist, can't jail devices.

TEST=cargo check --all-features
TEST=FEATURES=test emerge-amd64-generic crosvm

Change-Id: I77122c7d6861b2d610de2fff718896918ab21e10
Reviewed-on: https://chromium-review.googlesource.com/1469225
Commit-Ready: David Tolnay <dtolnay@chromium.org>
Tested-by: David Tolnay <dtolnay@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2019-02-20 08:20:02 -08:00
..
examples fix warning and bit rotted tests uncovered by kokoro 2018-09-22 01:43:11 -07:00
protocol gpu_display: provides wayland based output for virtio-gpu 2018-07-09 15:48:21 -07:00
src error: Print errors using Display impl 2019-02-20 08:20:02 -08:00
build.rs cargo fmt all source code 2018-10-09 21:14:05 -07:00
Cargo.toml crosvm: Support cros-rust version crosvm ebuild 2019-01-22 16:53:13 -08:00