Erik Schilling 2143bcb44c tree-wide: continue unwinds on join failures ... The error from joining a thread is a bit confusing. It is only printed if the other thread panicked. This means, effectively, we only get here if something called .unwrap(), .expect() or panicked in a different way. In these cases an (ugly) error was already printend. Printing a pretty message about the join failure does not really help a lot... So let's just continue the unwind as suggested by the docs on the join `Result` [1]. Before: thread '<unnamed>' panicked at 'Test panic', crates/gpio/src/backend.rs:146:13 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Any { .. }', crates/gpio/src/backend.rs:176:23 After: thread '<unnamed>' panicked at 'Test panic', crates/gpio/src/backend.rs:146:13 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [1]: https://doc.rust-lang.org/std/thread/type.Result.html Signed-off-by: Erik Schilling <erik.schilling@linaro.org>		2023-11-20 13:05:48 +05:30
..
backend.rs	tree-wide: continue unwinds on join failures	2023-11-20 13:05:48 +05:30
gpio.rs	Move all crates to workspace root	2023-10-16 12:03:57 +05:30
main.rs	Move all crates to workspace root	2023-10-16 12:03:57 +05:30
mock_gpio.rs	Move all crates to workspace root	2023-10-16 12:03:57 +05:30
vhu_gpio.rs	Update vhost-user-backend to 0.11 series	2023-11-14 10:48:19 +02:00
virtio_gpio.rs	Move all crates to workspace root	2023-10-16 12:03:57 +05:30