clockworklabs / clockworklabs/SpacetimeDB
CI flake: Smoketests (Windows 2/4) / cluster::cli::publish::cli_can_publish_breaking_change_with_delete_data_flag
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:
cluster::cli::publish::cli_can_publish_breaking_change_with_delete_data_flag
Error:
thread 'cluster::cli::publish::cli_can_publish_breaking_change_with_delete_data_flag' (6448) panicked at crates\smoketests\tests\cluster\cli\publish.rs:68:10:
called Result::unwrap() on an Err value: spacetime ["publish", "--module-path", "C:\actions-runner\_work\SpacetimeDB\SpacetimeDB\modules\module-test", "--server", "http://127.0.0.1:50214", "--yes=remote",...
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/34253018158/job/102161276745 (Smoketests (Windows 2/4), attempt 1 -> 2)
Timeout detection:
- none
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 crates\smoketests\tests\cluster\cli\publish.rs, especially the unwrap at line 68 and the named test. Review the failed Windows GitHub Actions run and the publish command error, then reproduce the failure if possible. Done means the test reliably passes on the Windows smoketest job and the flake is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100