oasisprotocol / oasisprotocol/oasis-core
Rust tests fail under tarpaulin
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Relevant section of most recent CI log appears to be:
Processing ekiden-storage-batch
Launching test
running /root/project/target/debug/deps/ekiden_storage_batch-d66081ef95292753
running 1 test
test backend::test::test_batch ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Error occurred when handling ptrace event: ESRCH: No such process
Processing ekiden-enclave-common
Launching test
running /root/project/target/debug/deps/ekiden_enclave_common-460abce2f57fcf07
Unexpected signal when starting test
running 2 tests
test quote::tests::test_pem_parse_many ... ok
test quote::tests::test_validate_avr_signature ... ok
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
so it's likely either the enclave_common or the storage_batch test that should be excluded or debugged in this context
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 with the tarpaulin CI run and the tests named in the log: ekiden-storage-batch's backend::test::test_batch and ekiden-enclave-common's quote tests. Investigate the ESRCH ptrace error and unexpected signal, then determine whether either test needs debugging or exclusion under tarpaulin. Done means the relevant Rust tests run successfully in that coverage context without the reported failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100