Skip to content

fix: resolve actor create build tags to the env instead of game (#1430) #69

fix: resolve actor create build tags to the env instead of game (#1430)

fix: resolve actor create build tags to the env instead of game (#1430) #69

Triggered via push November 22, 2024 03:15
Status Failure
Total duration 1h 12m 43s
Artifacts

docker.yaml

on: push
Matrix: build-and-push-client
Matrix: build-and-push-monolith
Matrix: build-and-push-server
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 4 warnings
build-and-push-client (linux/x86_64, self-hosted, Linux, X64)
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cd packages/infra/client && \tRUSTFLAGS=\"--cfg tokio_unstable\" cargo build -vv --release --bin rivet-client --bin rivet-isolate-v8-runner --bin rivet-container-runner && \tmkdir -p /app/dist && \tmv target/release/rivet-client target/release/rivet-isolate-v8-runner target/release/rivet-container-runner /app/dist/" did not complete successfully: exit code: 101
build-and-push-client (linux/arm64, self-hosted, Linux, ARM64)
The job was canceled because "linux_x86_64_self-hosted_" failed.
build-and-push-client (linux/arm64, self-hosted, Linux, ARM64)
The operation was canceled.
build-and-push-monolith (linux/x86_64, self-hosted, Linux, X64)
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cd packages/infra/client && RUSTFLAGS=\"--cfg tokio_unstable\" cargo build -v --release --bin rivet-client --bin rivet-isolate-v8-runner --bin rivet-container-runner && mkdir -p /app/dist && mv target/release/rivet-client target/release/rivet-isolate-v8-runner target/release/rivet-container-runner /app/dist/" did not complete successfully: exit code: 101
build-and-push-monolith (linux/arm64, self-hosted, Linux, ARM64)
The job was canceled because "linux_x86_64_self-hosted_" failed.
build-and-push-monolith (linux/arm64, self-hosted, Linux, ARM64)
The operation was canceled.
build-and-push-client (linux/x86_64, self-hosted, Linux, X64)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-push-monolith (linux/x86_64, self-hosted, Linux, X64)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-push-server (linux/x86_64, self-hosted, Linux, X64)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-push-server (linux/arm64, self-hosted, Linux, ARM64)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/