tests fail on M1
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
Hey there, I've been trying for the past few hours to figure out this one but couldn't solve it on my own. Basically running
cargo test
result in
running 156 tests
test attr::tests::attr_value_always_bytes ... ok
test attr::tests::attr_value_from_string ... ok
test attr::tests::attr_value_from_bytes ... ok
test attr::tests::attr_value_partial_eq ... ok
dyld: lazy symbol binding failed: Symbol not found: ___aarch64_ldadd4_acq_rel
Referenced from: /private/tmp/git2-rs/target/debug/deps/git2-72ec4e13db094535
Expected in: flat namespace
dyld: Symbol not found: ___aarch64_ldadd4_acq_rel
Referenced from: /private/tmp/git2-rs/target/debug/deps/git2-72ec4e13db094535
Expected in: flat namespace
error: test failed, to rerun pass '--lib'
Caused by:
process didn't exit successfully: `/private/tmp/git2-rs/target/debug/deps/git2-72ec4e13db094535` (signal: 6, SIGABRT: process abort signal)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on an M1 system with cargo test and inspect the dyld error for the missing ___aarch64_ldadd4_acq_rel symbol in the generated git2 test binary. Trace the platform or linker configuration involved; done means the full test suite completes successfully on M1 without the abort.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100