rust/tests/ui/custom_ice_message.stderr

thread 'rustc' panicked at 'Testing the ICE message', clippy_lints/src/utils/internal_lints.rs
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new

note: Clippy version: foo
Use rustc_env instead of exec_env for test 2019-10-09 00:45:05 -05:00			`thread 'rustc' panicked at 'Testing the ICE message', clippy_lints/src/utils/internal_lints.rs`
Update custom_ice_message.stderr 2020-01-16 09:01:31 -06:00			note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Add custom ICE message that points to Clippy repo This utilizes https://github.com/rust-lang/rust/pull/60584 by setting our own `panic_hook` and pointing to our own issue tracker instead of the rustc issue tracker. This also adds a new internal lint to test the ICE message. Potential downsides * This essentially copies rustc's `report_ice` function as `report_clippy_ice`. I think that's how it's meant to be implemented, but maybe @jonas-schievink could have a look as well =) The downside of more-or-less copying this function is that we have to maintain it as well now. The original function can be found [here][original]. * `driver` now depends directly on `rustc` and `rustc_errors` Closes #2734 [original]: https://github.com/rust-lang/rust/blob/59367b074f1523353dddefa678ffe3cac9fd4e50/src/librustc_driver/lib.rs#L1185 2019-09-27 00:09:12 -05:00
			`error: internal compiler error: unexpected panic`

			`note: the compiler unexpectedly panicked. this is a bug.`

			`note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new`

Use exec_env to set backtrace level and normalize output 2019-10-08 14:25:10 -05:00			`note: Clippy version: foo`
Add custom ICE message that points to Clippy repo This utilizes https://github.com/rust-lang/rust/pull/60584 by setting our own `panic_hook` and pointing to our own issue tracker instead of the rustc issue tracker. This also adds a new internal lint to test the ICE message. Potential downsides * This essentially copies rustc's `report_ice` function as `report_clippy_ice`. I think that's how it's meant to be implemented, but maybe @jonas-schievink could have a look as well =) The downside of more-or-less copying this function is that we have to maintain it as well now. The original function can be found [here][original]. * `driver` now depends directly on `rustc` and `rustc_errors` Closes #2734 [original]: https://github.com/rust-lang/rust/blob/59367b074f1523353dddefa678ffe3cac9fd4e50/src/librustc_driver/lib.rs#L1185 2019-09-27 00:09:12 -05:00