clockworklabs / clockworklabs/SpacetimeDB
CI flake: unity-testsuite
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
unity-testsuite
Error:
The job has exceeded the maximum execution time of 30m0s
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/29064277650/job/86274837342 (unity-testsuite, attempt 1 -> 2)
Timeout detection:
- Source: check-run annotation
- Inferred: no
- Detail: The job has exceeded the maximum execution time of 30m0s
Context:
- none
Contributor guide
No contributing guide indexed for this repository
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 linked failed GitHub Actions run for the unity-testsuite job and compare it with the successful rerun. Identify why the job exceeds the 30-minute limit, then verify that the unity-testsuite completes within the limit reliably without relying on a rerun.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust, unity
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100