clockworklabs / clockworklabs/SpacetimeDB
CI flake: unity-testsuite - 502 pulling Unity editor
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 manually from a GitHub Actions run requested in #ci-gremlin.
Tests:
unity-testsuite
Error:
Docker failed while pulling the Unity editor image from Docker Hub:
docker: unknown: failed to copy: httpReadSeeker: failed open: unexpected status from GET request to https://registry-1.docker.io/v2/unityci/editor/blobs/sha256:196ea3960e275155a3d719affa851630a44d3333481958999ad3e66d6e6e7055: 502 Bad Gateway
The process '/usr/bin/docker' failed with exit code 125
Failed job run:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/27349101052/job/80806362277 (
unity-testsuite, merge queue run, commitc0d1c9dac306ceec1477403777a950729cb46a94)
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 by inspecting the linked GitHub Actions run, especially the unity-testsuite job and its Docker pull failure. Check whether the Unity editor image fetch issue is reproducible; the issue names no repository file or proposed remediation, so completion criteria need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, unity
- Domain
- ci-cd, game-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100