Test failures on aarch64
investigate
I get this output for `cargo test --target=aarch64-unknown-linux-gnu`, which I don't get when running via `x86_64` normally:
```
---- process::tests::handle_external_command_not_executable stdout ----
thread 'process::tests::handle_external_command_not_executable' panicked at src/test_helpers/assertions/assert_results.rs:98:5:
assertion failed: `(left == right)`
Diff < left / right > :
<[
< Error(Unable to run /work/build/makepkg/git-interactive-rebase-tool/src/git-interactive-rebase-tool/test/not-executable.sh : File not executable: /work/build/makepkg/git-interactive-rebase-tool/src/git-interactive-rebase-tool/test/not-executable.sh, Some(List)),
<]
>[]
---- process::tests::handle_external_command_not_found stdout ----
thread 'process::tests::handle_external_command_not_found' panicked at src/test_helpers/assertions/assert_results.rs:98:5:
assertion failed: `(left == right)`
Diff < left / right > :
<[
< Error(Unable to run /work/build/makepkg/git-interactive-rebase-tool/src/git-interactive-rebase-tool/test/not-found.sh : File does not exist: /work/build/makepkg/git-interactive-rebase-tool/src/git-interactive-rebase-tool/test/not-found.sh, Some(List)),
<]
>[]
failures:
process::tests::handle_external_command_not_executable
process::tests::handle_external_command_not_found
```
I'm not quite sure if this indicates a bug in this program or a shortcoming of some dependency's implementation, but I don't know enough about the way the tool is designed to tell. Right now I'm running these tests via qemu rather than actual hardware, but I assume it shouldn't make a difference.
1 条评论