AI Game Developer update #40
IvanMurzakrelease.yml
on: push
check-version-tag
12s
Matrix: test-unity-2022-3-62f3-editmode / test
Matrix: test-unity-2022-3-62f3-playmode / test
Matrix: test-unity-2022-3-62f3-standalone / test
Matrix: test-unity-2023-2-22f1-editmode / test
Matrix: test-unity-2023-2-22f1-playmode / test
Matrix: test-unity-2023-2-22f1-standalone / test
Matrix: test-unity-6000-3-1f1-editmode / test
Matrix: test-unity-6000-3-1f1-playmode / test
Matrix: test-unity-6000-3-1f1-standalone / test
cleanup-artifacts
4s
Annotations
18 errors and 39 warnings
|
test-unity-2023-2-22f1-editmode / 2023.2.22f1 editmode on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2023-2-22f1-playmode / 2023.2.22f1 playmode on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2022-3-62f3-editmode / 2022.3.62f3 editmode on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2023-2-22f1-playmode / 2023.2.22f1 playmode on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2022-3-62f3-editmode / 2022.3.62f3 editmode on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-6000-3-1f1-standalone / 6000.3.1f1 standalone on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-6000-3-1f1-playmode / 6000.3.1f1 playmode on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2022-3-62f3-playmode / 2022.3.62f3 playmode on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2023-2-22f1-editmode / 2023.2.22f1 editmode on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2022-3-62f3-playmode / 2022.3.62f3 playmode on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-6000-3-1f1-standalone / 6000.3.1f1 standalone on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-6000-3-1f1-playmode / 6000.3.1f1 playmode on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on base
The process '/usr/bin/docker' failed with exit code 1
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on windows-mono
The process '/usr/bin/docker' failed with exit code 1
|
|
check-version-tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mukunku/tag-exists-action@v1.6.0, WyriHaximus/github-action-get-previous-tag@v1. 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/
|
|
build-unity-installer
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/upload-artifact@v4, game-ci/unity-builder@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2023-2-22f1-editmode / 2023.2.22f1 editmode on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2023-2-22f1-playmode / 2023.2.22f1 playmode on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2022-3-62f3-editmode / 2022.3.62f3 editmode on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2023-2-22f1-playmode / 2023.2.22f1 playmode on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2022-3-62f3-editmode / 2022.3.62f3 editmode on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-standalone / 6000.3.1f1 standalone on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-playmode / 6000.3.1f1 playmode on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2022-3-62f3-playmode / 2022.3.62f3 playmode on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on base
Activation failed, attempting retry #2
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on base
Activation failed, attempting retry #1
|
|
test-unity-2023-2-22f1-editmode / 2023.2.22f1 editmode on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2023-2-22f1-editmode / 2023.2.22f1 editmode on windows-mono
Activation failed, attempting retry #2
|
|
test-unity-2023-2-22f1-editmode / 2023.2.22f1 editmode on windows-mono
Activation failed, attempting retry #1
|
|
test-unity-2022-3-62f3-playmode / 2022.3.62f3 playmode on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2022-3-62f3-playmode / 2022.3.62f3 playmode on windows-mono
Activation failed, attempting retry #2
|
|
test-unity-2022-3-62f3-playmode / 2022.3.62f3 playmode on windows-mono
Activation failed, attempting retry #1
|
|
test-unity-6000-3-1f1-standalone / 6000.3.1f1 standalone on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-standalone / 6000.3.1f1 standalone on windows-mono
Activation failed, attempting retry #1
|
|
test-unity-6000-3-1f1-playmode / 6000.3.1f1 playmode on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-playmode / 6000.3.1f1 playmode on windows-mono
Activation failed, attempting retry #2
|
|
test-unity-6000-3-1f1-playmode / 6000.3.1f1 playmode on windows-mono
Activation failed, attempting retry #1
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on base
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on windows-mono
Activation failed, attempting retry #3
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on base
Activation failed, attempting retry #3
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on base
Activation failed, attempting retry #2
|
|
test-unity-2022-3-62f3-standalone / 2022.3.62f3 standalone on base
Activation failed, attempting retry #1
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on windows-mono
Activation failed, attempting retry #2
|
|
test-unity-2023-2-22f1-standalone / 2023.2.22f1 standalone on windows-mono
Activation failed, attempting retry #1
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on windows-mono
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/upload-artifact@v4, game-ci/unity-test-runner@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/
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on windows-mono
Activation failed, attempting retry #3
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on windows-mono
Activation failed, attempting retry #2
|
|
test-unity-6000-3-1f1-editmode / 6000.3.1f1 editmode on windows-mono
Activation failed, attempting retry #1
|
|
cleanup-artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: geekyeggo/delete-artifact@v5. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Test results for 2022.3.62f3 editmode on base
Expired
|
12.4 KB |
sha256:5f690717d05010d8639164e2860e39c4ce2ea2a0ce0e3034bbafb920eb4f727a
|
|
|
Test results for 2022.3.62f3 editmode on windows-mono
Expired
|
12.4 KB |
sha256:b43c4271d5cccbb48ae8dc65fdd6abf021ce8ef579bd8f105446c3a68a6e4295
|
|
|
Test results for 2022.3.62f3 playmode on base
Expired
|
12.4 KB |
sha256:402df706c0d8e6b8e49c94d9a07ae47b3e694944d0531f0d0f4b01860b70b049
|
|
|
Test results for 2022.3.62f3 playmode on windows-mono
Expired
|
12.3 KB |
sha256:933e34148d85052d48f4b010bae5a67485bf073de212f1525d470798a742eda0
|
|
|
Test results for 2022.3.62f3 standalone on base
Expired
|
12.8 KB |
sha256:8533b4855b211540ee2aa5ae4a79974ad0aea2ba5e5b013c065bc260389992cd
|
|
|
Test results for 2022.3.62f3 standalone on windows-mono
Expired
|
12.5 KB |
sha256:7dd37d0f0d83d12dc82925bff8b0d101a908ead1180c3da1bacae5a672cd008a
|
|
|
Test results for 2023.2.22f1 editmode on base
Expired
|
22.9 KB |
sha256:d3f47a76179d86539744755717d51daaa010799f39247c0c3ccb0b9df36fe044
|
|
|
Test results for 2023.2.22f1 editmode on windows-mono
Expired
|
22.9 KB |
sha256:a6f7785783500fec73d817cbffbbf8ee02c2b28edf85f72156c62a9aa113e601
|
|
|
Test results for 2023.2.22f1 playmode on base
Expired
|
22.8 KB |
sha256:51464d8c96bf71d29ce3b37a118c073edaa10bec6d1cedbde20ef02a6cd0278c
|
|
|
Test results for 2023.2.22f1 playmode on windows-mono
Expired
|
22.7 KB |
sha256:c921867f70cf3bec40b3c9603c528fe5fd56bf20bd5ce195f32c71e50f8a87a7
|
|
|
Test results for 2023.2.22f1 standalone on base
Expired
|
22.9 KB |
sha256:ca0ddf2700f09b401f3cd7b1ad901231f0363dfad2aac8f4283dc9bc75c3cb4a
|
|
|
Test results for 2023.2.22f1 standalone on windows-mono
Expired
|
22.6 KB |
sha256:5f1467fdc3e180bd70411aa910a9f4cd5c9a766334e554715ff8971af2a65814
|
|
|
Test results for 6000.3.1f1 editmode on base
Expired
|
14.5 KB |
sha256:7f4363ec51c29a011d474ca6bc0038a5722199fd90935f410cb4f3ac65e0fe69
|
|
|
Test results for 6000.3.1f1 editmode on windows-mono
Expired
|
14.7 KB |
sha256:8ad27cb2b5e8eccf354728b388a1a96ede8b3d0f5dfb865cb0d843543a18e866
|
|
|
Test results for 6000.3.1f1 playmode on base
Expired
|
14.5 KB |
sha256:541dfa8dd4ffb8575b5ab16205325c607ce8e465a9730d9da213d7407b8398be
|
|
|
Test results for 6000.3.1f1 playmode on windows-mono
Expired
|
14.6 KB |
sha256:fec6da5ea4f6e464b38f9b3110d863618c025e7223345f2dd92d57792ab61ddf
|
|
|
Test results for 6000.3.1f1 standalone on base
Expired
|
14.6 KB |
sha256:d7a72e6d2480159e38722089dbde72ecc181a1f8448eef2d26c4223022985a31
|
|
|
Test results for 6000.3.1f1 standalone on windows-mono
Expired
|
14.8 KB |
sha256:9bdac5d282268787fe808dbc07e5c693000e485b535f3cf206252b03dd6158c4
|
|