Describe the bug
When running cargo test on s390x (a big-endian architecture), several failures occur:
failures:
---- write::test::fuzz_crash_2024_07_17 stdout ----
Error: InvalidArchive("Could not find EOCD")
---- write::test::fuzz_crash_2024_07_19 stdout ----
Error: InvalidArchive("Could not find EOCD")
---- write::test::test_deep_copy stdout ----
thread 'write::test::test_deep_copy' panicked at src/write.rs:2282:53:
called `Result::unwrap()` on an `Err` value: InvalidArchive("Could not find EOCD")
---- write::test::test_fuzz_crash_2024_06_17a stdout ----
Error: InvalidArchive("Could not find EOCD")
---- write::test::test_fuzz_failure_2024_06_08 stdout ----
Error: InvalidArchive("Could not find EOCD")
---- write::test::test_fuzz_crash_2024_06_18b stdout ----
Error: FileNotFound
failures:
write::test::fuzz_crash_2024_07_17
write::test::fuzz_crash_2024_07_19
write::test::test_deep_copy
write::test::test_fuzz_crash_2024_06_17a
write::test::test_fuzz_crash_2024_06_18b
write::test::test_fuzz_failure_2024_06_08
test result: FAILED$<2>. 111 passed; 6 failed; 0 ignored; 0 measured; 0 filtered out; finished in 7.31s
To Reproduce
Steps to reproduce the behavior:
- Work on real
s390x hardware, in a virtual machine under qemu-system emulation, or in a chroot (e.g. a mock chroot) under qemu-user-static emulation.
git clone https://github.com/zip-rs/zip2.gitcd zip2cargo test
Expected behavior
All tests pass.
Screenshots
N/A
Desktop (please complete the following information):
- OS: Fedora Linux (Rawhide)
- Browser N/A
- Version
zip2 2.2.3, c6ba201
Additional context
These failures were first observed on real hardware while working on a proposed update to the rust-zip package in Fedora, then were reproduced in emulation. I have non-interactive access to test proposed patches on real hardware (via RPM package test-builds), and I can easily do interactive experiments in an emulated chroot. Please let me know if there’s anything else I can provide that would make this easier to understand and fix.
Describe the bug
When running
cargo testons390x(a big-endian architecture), several failures occur:To Reproduce
Steps to reproduce the behavior:
s390xhardware, in a virtual machine underqemu-systememulation, or in a chroot (e.g. a mock chroot) underqemu-user-staticemulation.git clone https://github.com/zip-rs/zip2.gitcd zip2cargo testExpected behavior
All tests pass.
Screenshots
N/A
Desktop (please complete the following information):
zip22.2.3, c6ba201Additional context
These failures were first observed on real hardware while working on a proposed update to the
rust-zippackage in Fedora, then were reproduced in emulation. I have non-interactive access to test proposed patches on real hardware (via RPM package test-builds), and I can easily do interactive experiments in an emulated chroot. Please let me know if there’s anything else I can provide that would make this easier to understand and fix.