Process completed with exit code 1.

Error: retained-workspace- already exists ❯ Function.CreateWorkspace src/model/orchestrator/services/core/shared-workspace-locking.ts:342:13 ❯ Function.GetLockedWorkspace src/model/orchestrator/services/core/shared-workspace-locking.ts:193:26 ❯ Function.runWithProvider src/model/orchestrator/orchestrator.ts:323:24 ❯ Function.run src/model/orchestrator/orchestrator.ts:282:14 ❯ src/model/orchestrator/tests/e2e/orchestrator-end2end-retaining.test.ts:99:30

Orchestrator failed: retained-workspace- already exists

{ "name": "Error", "message": "retained-workspace- already exists", "stack": "Error: retained-workspace- already exists\n at Function.CreateWorkspace (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/services/core/shared-workspace-locking.ts:342:13)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Function.GetLockedWorkspace (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/services/core/shared-workspace-locking.ts:193:26)\n at Function.runWithProvider (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:323:24)\n at Function.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:282:14)\n at /home/runner/work/unity-builder/unity-builder/src/model/orchestrator/tests/e2e/orchestrator-end2end-retaining.test.ts:99:30\n at file:///home/runner/work/unity-builder/unity-builder/node_modules/@vitest/runner/dist/chunk-artifact.js:1903:20" }

Process completed with exit code 1.

AssertionError: expected 'orchestrator build workflow starting\…' to contain 'Activation successful' - Expected + Received - Activation successful + orchestrator build workflow starting + CACHE_KEY=test-case-f57358ce-8b51-42a6-bc3f-0f2fb4a49d0a + game ci start + E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied) + E: Unable to lock directory /var/lib/apt/lists/ + E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) + E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? + /data/cache [error opening dir] + + 0 directories, 0 files + ❯ src/model/orchestrator/tests/e2e/orchestrator-end2end-caching.test.ts:101:24

Process completed with exit code 1.

Error: Build failed with exit code 1 ❯ LocalDockerOrchestrator.runTaskInWorkflow src/model/orchestrator/providers/docker/index.ts:348:13 ❯ Function.standardBuildAutomation src/model/orchestrator/workflows/build-automation-workflow.ts:42:15 ❯ BuildAutomationWorkflow.run src/model/orchestrator/workflows/build-automation-workflow.ts:15:12 ❯ WorkflowCompositionRoot.run src/model/orchestrator/workflows/workflow-composition-root.ts:31:14 ❯ Function.runWithProvider src/model/orchestrator/orchestrator.ts:344:22 ❯ Function.run src/model/orchestrator/orchestrator.ts:282:14 ❯ src/model/orchestrator/tests/e2e/orchestrator-end2end-caching.test.ts:61:29

Orchestrator failed: Build failed with exit code 1

{ "name": "Error", "message": "Build failed with exit code 1", "stack": "Error: Build failed with exit code 1\n at LocalDockerOrchestrator.runTaskInWorkflow (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/providers/docker/index.ts:348:13)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Function.standardBuildAutomation (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/build-automation-workflow.ts:42:15)\n at BuildAutomationWorkflow.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/build-automation-workflow.ts:15:12)\n at WorkflowCompositionRoot.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/workflow-composition-root.ts:31:14)\n at Function.runWithProvider (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:344:22)\n at Function.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:282:14)\n at /home/runner/work/unity-builder/unity-builder/src/model/orchestrator/tests/e2e/orchestrator-end2end-caching.test.ts:61:29\n at file:///home/runner/work/unity-builder/unity-builder/node_modules/@vitest/runner/dist/chunk-artifact.js:1903:20" }

no CLI mode found for remote-cli-pre-build

Process completed with exit code 1.

Error: Build failed with exit code 1 ❯ LocalDockerOrchestrator.runTaskInWorkflow src/model/orchestrator/providers/docker/index.ts:348:13 ❯ Function.standardBuildAutomation src/model/orchestrator/workflows/build-automation-workflow.ts:42:15 ❯ BuildAutomationWorkflow.run src/model/orchestrator/workflows/build-automation-workflow.ts:15:12 ❯ WorkflowCompositionRoot.run src/model/orchestrator/workflows/workflow-composition-root.ts:31:14 ❯ Function.runWithProvider src/model/orchestrator/orchestrator.ts:344:22 ❯ Function.run src/model/orchestrator/orchestrator.ts:282:14 ❯ src/model/orchestrator/tests/e2e/orchestrator-end2end-retaining.test.ts:52:29

Orchestrator failed: Build failed with exit code 1

{ "name": "Error", "message": "Build failed with exit code 1", "stack": "Error: Build failed with exit code 1\n at LocalDockerOrchestrator.runTaskInWorkflow (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/providers/docker/index.ts:348:13)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Function.standardBuildAutomation (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/build-automation-workflow.ts:42:15)\n at BuildAutomationWorkflow.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/build-automation-workflow.ts:15:12)\n at WorkflowCompositionRoot.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/workflow-composition-root.ts:31:14)\n at Function.runWithProvider (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:344:22)\n at Function.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:282:14)\n at /home/runner/work/unity-builder/unity-builder/src/model/orchestrator/tests/e2e/orchestrator-end2end-retaining.test.ts:52:29\n at file:///home/runner/work/unity-builder/unity-builder/node_modules/@vitest/runner/dist/chunk-artifact.js:1903:20" }

no CLI mode found for remote-cli-pre-build

Process completed with exit code 1.

Error: Build failed with exit code 1 ❯ LocalDockerOrchestrator.runTaskInWorkflow src/model/orchestrator/providers/docker/index.ts:348:13 ❯ Function.standardBuildAutomation src/model/orchestrator/workflows/build-automation-workflow.ts:42:15 ❯ BuildAutomationWorkflow.run src/model/orchestrator/workflows/build-automation-workflow.ts:15:12 ❯ WorkflowCompositionRoot.run src/model/orchestrator/workflows/workflow-composition-root.ts:31:14 ❯ Function.runWithProvider src/model/orchestrator/orchestrator.ts:344:22 ❯ Function.run src/model/orchestrator/orchestrator.ts:282:14 ❯ src/model/orchestrator/tests/e2e/orchestrator-end2end-caching.test.ts:61:29

Orchestrator failed: Build failed with exit code 1

{ "name": "Error", "message": "Build failed with exit code 1", "stack": "Error: Build failed with exit code 1\n at LocalDockerOrchestrator.runTaskInWorkflow (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/providers/docker/index.ts:348:13)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Function.standardBuildAutomation (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/build-automation-workflow.ts:42:15)\n at BuildAutomationWorkflow.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/build-automation-workflow.ts:15:12)\n at WorkflowCompositionRoot.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/workflows/workflow-composition-root.ts:31:14)\n at Function.runWithProvider (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:344:22)\n at Function.run (/home/runner/work/unity-builder/unity-builder/src/model/orchestrator/orchestrator.ts:282:14)\n at /home/runner/work/unity-builder/unity-builder/src/model/orchestrator/tests/e2e/orchestrator-end2end-caching.test.ts:61:29\n at file:///home/runner/work/unity-builder/unity-builder/node_modules/@vitest/runner/dist/chunk-artifact.js:1903:20" }

no CLI mode found for remote-cli-pre-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, azure/setup-kubectl@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/