rust/tests/rustdoc-ui/failed-doctest-output.stdout


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

failures:

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

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
Couldn't compile the test.
---- $DIR/failed-doctest-output.rs - SomeStruct (line 15) stdout ----
Test executable failed (exit status: 101).

stdout:
stdout 1
stdout 2

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


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

test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
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`
Fix line numbers 2022-04-11 11:26:05 -05:00			`test $DIR/failed-doctest-output.rs - OtherStruct (line 25) ... FAILED`
			`test $DIR/failed-doctest-output.rs - SomeStruct (line 15) ... FAILED`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
			`failures:`

Fix line numbers 2022-04-11 11:26:05 -05:00			`---- $DIR/failed-doctest-output.rs - OtherStruct (line 25) stdout ----`
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00			error[E0425]: cannot find value `no` in this scope
Fix line numbers 2022-04-11 11:26:05 -05:00			`--> $DIR/failed-doctest-output.rs:26:1`
rustdoc: forward -Z options to rustc Currently rustdoc does not forward `-Z` options to rustc when building test executables. This makes impossible to use rustdoc to run test samples when crate under test is instrumented with one of sanitizers `-Zsanitizer=...`, since the final linking step will not include sanitizer runtime library. Forward `-Z` options to rustc to solve the issue. Helps with #43031. 2019-10-10 19:00:00 -05:00			`\|`
			`LL \| no`
			`\| ^^ not found in this scope`
report doctest compile failures correctly 2018-07-09 19:11:06 -05:00
Make the rustc driver and interface demand driven 2018-12-08 13:30:23 -06:00			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0425`.
do not print panic message on doctest failures 2019-05-04 14:37:12 -05:00			`Couldn't compile the test.`
Fix line numbers 2022-04-11 11:26:05 -05:00			`---- $DIR/failed-doctest-output.rs - SomeStruct (line 15) stdout ----`
Fix test case 2022-04-07 16:25:16 -05:00			`Test executable failed (exit status: 101).`
do not print panic message on doctest failures 2019-05-04 14:37:12 -05:00
			`stdout:`
			`stdout 1`
			`stdout 2`

			`stderr:`
			`stderr 1`
			`stderr 2`
			`thread 'main' panicked at 'oh no', $DIR/failed-doctest-output.rs:7:1`
Update `output-default.json` and rustdoc test 2020-01-10 12:24:34 -06: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
add ui test for failing doctest 2018-07-09 14:26:22 -05:00

			`failures:`
Fix line numbers 2022-04-11 11:26:05 -05:00			`$DIR/failed-doctest-output.rs - OtherStruct (line 25)`
			`$DIR/failed-doctest-output.rs - SomeStruct (line 15)`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00
libtest: Print the total time taken to execute a test suite 2020-11-26 14:15:15 -06:00			`test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME`
add ui test for failing doctest 2018-07-09 14:26:22 -05:00