internal::test::internal_macro_test panic on gentoo
Summary
failures:
---- internal::test::internal_macro_test stdout ----
thread 'internal::test::internal_macro_test' panicked at 'assertion failed: s.contains(\"internal_macro_test\")', crates/tor-error/src/internal.rs:283:9
stack backtrace:
0: 0x5604047d5a40 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h83655fbab46be21c
1: 0x5604047904dc - core::fmt::write::hfaad550dc1939974
2: 0x5604047d6fd0 - std::io::Write::write_fmt::h91216bc5e7f92ae8
3: 0x5604047d68b5 - std::panicking::default_hook::{{closure}}::h6b7b1402ef52d940
4: 0x5604047d7843 - std::panicking::rust_panic_with_hook::h5510ecc615850ad6
5: 0x5604047d71eb - std::panicking::begin_panic_handler::{{closure}}::h334399dca2a96307
6: 0x5604047d7186 - std::sys_common::backtrace::__rust_end_short_backtrace::h5f8bc95899d58530
7: 0x5604047d7142 - rust_begin_unwind
8: 0x56040476d9e2 - core::panicking::panic_fmt::h874a94e22b671f7d
9: 0x56040476dadc - core::panicking::panic::h1961fe5c293cab15
10: 0x560404772448 - core::ops::function::FnOnce::call_once::h5b06ffa83349fb67
11: 0x5604047f6703 - test::__rust_begin_short_backtrace::hfdf6fcac833c37f7
12: 0x5604047f6a23 - test::run_test::run_test_inner::{{closure}}::h222a00634d2875e9
13: 0x5604047f968d - std::sys_common::backtrace::__rust_begin_short_backtrace::h7ec00303ddd26a14
14: 0x5604047f9400 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hf74bb18f2e5906f2
15: 0x5604047d7f15 - std::sys::unix::thread::Thread::new::thread_start::hfd4ca362db98cd5d
16: 0x7f19bc52b193 - <unknown>
17: 0x7f19bc5b0020 - __clone
18: 0x0 - <unknown>
Steps to reproduce:
Run tests via Gentoo's portage
What is the current bug behavior?
Test fails
What is the expected behavior?
Test should pass
Environment
- Version:
Arti 1.0.0
using runtime: TokioNativeTlsRuntime { .. }
optional features: <none>
- Operating system: Gentoo
- Install method: distribution package from git @ 3b24d051
Relevant logs and/or screenshots:
Attached: build-nocolor.log environment