Open PanJason opened 1 year ago
I have similar issues on both a WSL and a docker test of hermit on Ubuntu 22.04
#6 49.64 failures:
#6 49.64
#6 49.64 ---- rdrand_rdseed_is_masked stdout ----
#6 49.64 Expecting determinism:
#6 49.64 Test Run 1:
#6 49.64 thread 'rdrand_rdseed_is_masked' panicked at /Python-3.8.16/hermit/vendor/safeptrace/src/lib.rs:317:22:
#6 49.64 InvalidState(Wait(Exited(Pid(761), Signaled(SIGSEGV, false))))
#6 49.64 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
#6 49.64
#6 49.64 ---- getrandom_intercepted stdout ----
#6 49.64 Expecting determinism:
#6 49.64 Test Run 1:
#6 49.64 thread 'getrandom_intercepted' panicked at /Python-3.8.16/hermit/vendor/safeptrace/src/lib.rs:317:22:
#6 49.64 InvalidState(Wait(Exited(Pid(762), Signaled(SIGSEGV, false))))
#6 49.64
#6 49.64
#6 49.64 failures:
#6 49.64 getrandom_intercepted
#6 49.64 rdrand_rdseed_is_masked
#6 49.64
#6 49.64 test result: FAILED. 1 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s
#6 49.64
#6 49.65 error: test failed, to rerun pass `-p detcore --test tests_misc`
#6 ERROR: process "/bin/sh -c cargo test --release" did not complete successfully: exit code: 101
------
> [3/3] RUN cargo test --release:
#6 49.64 InvalidState(Wait(Exited(Pid(762), Signaled(SIGSEGV, false))))
#6 49.64
#6 49.64
#6 49.64 failures:
#6 49.64 getrandom_intercepted
#6 49.64 `rdrand_rdseed_is_masked`
Describe the bug A clear and concise description of what the bug is. I cloned hermit on the server and ran the
cargo test
. There are two failed tests.Indicate any of these common scenarios that apply:
To Reproduce Minimal input to reproduce the behavior.
cargo test
Expected behavior A clear and concise description of what you expected to happen.
all tests passed
Environment
uname -a
):Linux 5.14.0-rc5 #2 SMP Sat Jun 24 11:10:07 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux
/proce/cpuinfo
):Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz
/etc/issue
,/etc/redhat-release
):Ubuntu 20.04.4 LTS
Additional context Attach the logs to this issue as a text file generated by
hermit --log=trace --log-file=FOO run
.Add any other context about the problem here. I saw other people having a similar issue but he was running hermit inside a VM. That issue was because hermit cannot intercept CPUID instruction on VMs. Here I am running on a bare metal so I wonder what might be the reason here. Is it because of some CPU features? If that's the case, is there a list of supported CPUs by hermit. If this is a bug, I would also like to help fix it.