You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
---- cache_tests::stable_hash stdout ----
thread 'cache_tests::stable_hash' panicked at 'assertion failed: `(left == right)`
left: `"038D651019410545"`,
right: `"7D208C81E8236995"`', src/lib.rs:869:9
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:181:5
4: bkt::cache_tests::stable_hash
at ./src/lib.rs:869:9
5: bkt::cache_tests::stable_hash::{{closure}}
at ./src/lib.rs:868:5
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
This looks like it might be a big/small endian problem.
Thanks for the report, this test is mostly just a change-detector so it's probably simplest to disable it for this architecture (unless the errors you're seeing are non-deterministic which would be a bigger problem). Would you like to send a PR to disable this test?
Output:
This looks like it might be a big/small endian problem.
Build log: https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-bkt/34502277/log.gz
The text was updated successfully, but these errors were encountered: