spinframework / spinframework/spin
ci/code coverage: tarpaulin timing out
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
The code coverage automation has been failing recently and reliably with timeout errors, such as the following from this run:
Apr 01 03:48:58.262 ERROR cargo_tarpaulin: Failed to get test coverage! Error: Failed to run tests: Error: Timed out waiting for test response
Error: "Failed to get test coverage! Error: Failed to run tests: Error: Timed out waiting for test response"
Appears to have started with https://github.com/fermyon/spin/actions/runs/4548907012/jobs/8022361140
(Note this workflow is cron-triggered, so we don't have per-commit granularity on when it started to fail)
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 .github/workflows/code-coverage.yml and the linked GitHub Actions run, then inspect how cargo tarpaulin invokes the tests and where the timeout occurs. Reproduce or diagnose the failure and update the workflow or its coverage configuration so the cron-triggered code coverage job completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100