rust/src/test/rustdoc-ui/failed-doctest-output.stdout


running 2 tests
test $DIR/failed-doctest-output.rs - OtherStruct (line 27) ... FAILED
test $DIR/failed-doctest-output.rs - SomeStruct (line 21) ... FAILED

failures:

---- $DIR/failed-doctest-output.rs - OtherStruct (line 27) stdout ----
error[E0425]: cannot find value `no` in this scope
 --> $DIR/failed-doctest-output.rs:28:1
  |
3 | no
  | ^^ not found in this scope

thread '$DIR/failed-doctest-output.rs - OtherStruct (line 27)' panicked at 'couldn't compile the test', src/librustdoc/test.rs:326:13
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

---- $DIR/failed-doctest-output.rs - SomeStruct (line 21) stdout ----
thread '$DIR/failed-doctest-output.rs - SomeStruct (line 21)' panicked at 'test executable failed:

thread 'main' panicked at 'oh no', $DIR/failed-doctest-output.rs:3:1
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

', src/librustdoc/test.rs:361:17


failures:
    $DIR/failed-doctest-output.rs - OtherStruct (line 27)
    $DIR/failed-doctest-output.rs - SomeStruct (line 21)

test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00			`running 2 tests`
Set RUST_BACKTRACE=0 for rustdoc-ui/failed-doctest-output.rs This UI test is sensitive to backtrace output, so it should make sure that backtraces are not enabled by the environment. 2018-10-23 15:38:31 -07:00			`test $DIR/failed-doctest-output.rs - OtherStruct (line 27) ... FAILED`
			`test $DIR/failed-doctest-output.rs - SomeStruct (line 21) ... FAILED`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
			`failures:`

Set RUST_BACKTRACE=0 for rustdoc-ui/failed-doctest-output.rs This UI test is sensitive to backtrace output, so it should make sure that backtraces are not enabled by the environment. 2018-10-23 15:38:31 -07:00			`---- $DIR/failed-doctest-output.rs - OtherStruct (line 27) stdout ----`
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00			error[E0425]: cannot find value `no` in this scope
Set RUST_BACKTRACE=0 for rustdoc-ui/failed-doctest-output.rs This UI test is sensitive to backtrace output, so it should make sure that backtraces are not enabled by the environment. 2018-10-23 15:38:31 -07:00			`--> $DIR/failed-doctest-output.rs:28:1`
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00			`\|`
			`3 \| no`
			`\| ^^ not found in this scope`

Fixed line numbers in stderr file. 2018-12-07 20:46:10 +00:00			`thread '$DIR/failed-doctest-output.rs - OtherStruct (line 27)' panicked at 'couldn't compile the test', src/librustdoc/test.rs:326:13`
Update panic message to be clearer about env-vars Esteban Kuber requested that the panic message make it clear that `RUST_BACKTRACE=1` is an environment variable. This change makes that clear. Wording provided in part by David Tolnay. 2018-12-12 14:20:49 +00:00			note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00
Set RUST_BACKTRACE=0 for rustdoc-ui/failed-doctest-output.rs This UI test is sensitive to backtrace output, so it should make sure that backtraces are not enabled by the environment. 2018-10-23 15:38:31 -07:00			`---- $DIR/failed-doctest-output.rs - SomeStruct (line 21) stdout ----`
			`thread '$DIR/failed-doctest-output.rs - SomeStruct (line 21)' panicked at 'test executable failed:`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
update stdout file with test path normalization 2018-07-09 19:14:31 -05:00			`thread 'main' panicked at 'oh no', $DIR/failed-doctest-output.rs:3:1`
Update panic message to be clearer about env-vars Esteban Kuber requested that the panic message make it clear that `RUST_BACKTRACE=1` is an environment variable. This change makes that clear. Wording provided in part by David Tolnay. 2018-12-12 14:20:49 +00:00			note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
Fixed line numbers in stderr file. 2018-12-07 20:46:10 +00:00			`', src/librustdoc/test.rs:361:17`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00

			`failures:`
Set RUST_BACKTRACE=0 for rustdoc-ui/failed-doctest-output.rs This UI test is sensitive to backtrace output, so it should make sure that backtraces are not enabled by the environment. 2018-10-23 15:38:31 -07:00			`$DIR/failed-doctest-output.rs - OtherStruct (line 27)`
			`$DIR/failed-doctest-output.rs - SomeStruct (line 21)`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00			`test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00