Skip to content

Rename Cloud Runner to Orchestrator (#775) #1

Rename Cloud Runner to Orchestrator (#775)

Rename Cloud Runner to Orchestrator (#775) #1

Triggered via push March 13, 2026 20:03
Status Success
Total duration 1h 14m 37s
Artifacts
Tests
1m 54s
Tests
Orchestrator Integrity  /  Orchestrator Integrity Tests
1h 13m
Orchestrator Integrity / Orchestrator Integrity Tests
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 33 warnings
Orchestrator Integrity / Orchestrator Integrity Tests
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
::error ::No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
::error ::No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
::error ::No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER. See more info at https://game.ci/docs/github/activation
Orchestrator Integrity / Orchestrator Integrity Tests
Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
::error::Command failed: git checkout orchestrator-develop%0Aerror: pathspec 'orchestrator-develop' did not match any file(s) known to git%0A
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] error: pathspec 'orchestrator-develop' did not match any file(s) known to git
Orchestrator Integrity / Orchestrator Integrity Tests
[Client][Diagnostic] error: pathspec 'orchestrator-develop' did not match any file(s) known to git
Orchestrator Integrity / Orchestrator Integrity Tests
error: pathspec 'orchestrator-develop' did not match any file(s) known to git
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: git checkout orchestrator-develop
Orchestrator Integrity / Orchestrator Integrity Tests
Error: Command failed: gh auth status -t
Orchestrator Integrity / Orchestrator Integrity Tests
[Client] Error: Command failed: gh auth status -t
Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Tests
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Tests
Could not parse "abcd" to semver, defaulting android version code to 1
Tests
file.ext file2.ext
Tests
Changes were made to the following files and folders:
Tests
No valid version tags found. Using fallback description.
Tests
Failed to parse git describe output or version can not be determined through: "no-match-can-be-made".
Orchestrator Integrity / Orchestrator Integrity Tests
cache item doesn't exist /data/retained-workspace-1-linux64-v1rl/repo/test-project/Library
Orchestrator Integrity / Orchestrator Integrity Tests
cache item doesn't exist /data/retained-workspace-1-linux64-v1rl/repo/test-project/Library
Orchestrator Integrity / Orchestrator Integrity Tests
cache item 33898dbe0c436414633a7f293b7fcdab doesn't exist /data/retained-workspace-1-linux64-v1rl/repo/.git/lfs
Orchestrator Integrity / Orchestrator Integrity Tests
cache item doesn't exist /data/1-linux64-r3ix/repo/test-project/Library
Orchestrator Integrity / Orchestrator Integrity Tests
cache item doesn't exist /data/1-linux64-cs6u/repo/test-project/Library
Orchestrator Integrity / Orchestrator Integrity Tests
cache item 33898dbe0c436414633a7f293b7fcdab doesn't exist /data/1-linux64-cs6u/repo/.git/lfs
Orchestrator Integrity / Orchestrator Integrity Tests
cache item doesn't exist /data/1-linux64-b9jd/repo/test-project/Library
Orchestrator Integrity / Orchestrator Integrity Tests
cache item 33898dbe0c436414633a7f293b7fcdab doesn't exist /data/1-linux64-b9jd/repo/.git/lfs
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image exists on server node but not agent node. Pod will attempt to pull during scheduling. If pull fails due to disk pressure, ensure cleanup runs before this test.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image not cached on agent node (where pods run). Server node: has image. Disk info: /dev/root 145G 57G 88G 40% /var/lib/rancher/k3s. Pod will attempt to pull image (3.9GB) which may fail due to disk pressure.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image exists on server node but not agent node. Pod will attempt to pull during scheduling. If pull fails due to disk pressure, ensure cleanup runs before this test.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image not cached on agent node (where pods run). Server node: has image. Disk info: /dev/root 145G 56G 89G 39% /var/lib/rancher/k3s. Pod will attempt to pull image (3.9GB) which may fail due to disk pressure.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image exists on server node but not agent node. Pod will attempt to pull during scheduling. If pull fails due to disk pressure, ensure cleanup runs before this test.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image not cached on agent node (where pods run). Server node: has image. Disk info: /dev/root 145G 56G 89G 39% /var/lib/rancher/k3s. Pod will attempt to pull image (3.9GB) which may fail due to disk pressure.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image exists on server node but not agent node. Pod will attempt to pull during scheduling. If pull fails due to disk pressure, ensure cleanup runs before this test.
Orchestrator Integrity / Orchestrator Integrity Tests
Unity image not cached on agent node (where pods run). Server node: has image. Disk info: /dev/root 145G 56G 89G 39% /var/lib/rancher/k3s. Pod will attempt to pull image (3.9GB) which may fail due to disk pressure.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.
Orchestrator Integrity / Orchestrator Integrity Tests
Could not retrieve "Collected Logs" from pod after all attempts. Pod may have been killed before logs were written.