rust/tests/rustdoc-ui/doctest/edition-2024-error-output.stdout


running 1 test
test $DIR/edition-2024-error-output.rs - (line 14) ... FAILED

failures:

---- $DIR/edition-2024-error-output.rs - (line 14) stdout ----
Test executable failed (exit status: 101).

stderr:

thread 'main' ($TID) panicked at $TMP:6:1:
assertion `left == right` failed
  left: 4
 right: 5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    $DIR/edition-2024-error-output.rs - (line 14)

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME

all doctests ran in $TIME; merged doctests compilation took $TIME
Use `eprint!` instead of `eprintln!` 2025-04-03 17:58:59 +02:00
			`running 1 test`
Update rustdoc ui tests 2025-07-22 16:00:25 +02:00			`test $DIR/edition-2024-error-output.rs - (line 14) ... FAILED`
Use `eprint!` instead of `eprintln!` 2025-04-03 17:58:59 +02:00
			`failures:`

Update rustdoc ui tests 2025-07-22 16:00:25 +02:00			`---- $DIR/edition-2024-error-output.rs - (line 14) stdout ----`
Correctly display stdout and stderr in case a doctest is failing 2025-04-25 14:13:14 +02:00			`Test executable failed (exit status: 101).`

			`stderr:`
Use `eprint!` instead of `eprintln!` 2025-04-03 17:58:59 +02:00
Print thread ID in panic message if thread name is unknown `panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print. 2023-09-11 00:59:31 -04:00			`thread 'main' ($TID) panicked at $TMP:6:1:`
Use `eprint!` instead of `eprintln!` 2025-04-03 17:58:59 +02:00			assertion `left == right` failed
			`left: 4`
			`right: 5`
			note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


Correctly display stdout and stderr in case a doctest is failing 2025-04-25 14:13:14 +02:00
Use `eprint!` instead of `eprintln!` 2025-04-03 17:58:59 +02:00			`failures:`
Update rustdoc ui tests 2025-07-22 16:00:25 +02:00			`$DIR/edition-2024-error-output.rs - (line 14)`
Use `eprint!` instead of `eprintln!` 2025-04-03 17:58:59 +02:00
			`test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME`

Update rustdoc ui tests 2025-07-22 16:00:25 +02:00			`all doctests ran in $TIME; merged doctests compilation took $TIME`