🧪 Test (feat: add option to disable auto add to preloadedAssets) #148
test.yml
on: pull_request_target
⚙️ Setup
14s
Matrix: 🧪 Run tests
Annotations
16 errors and 107 warnings
|
🧪 Run tests (6000.3.13f1)
Build failed with exit code 125
|
|
🧪 Run tests (6000.2.15f1)
Build failed with exit code 134
|
|
🧪 Run tests (6000.0.72f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (6000.0.72f1)
No graphic device is available to show the window.
|
|
🧪 Run tests (6000.0.72f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (6000.5.0b2)
Build failed with exit code 1
|
|
🧪 Run tests (6000.1.17f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (6000.1.17f1)
No graphic device is available to show the window.
|
|
🧪 Run tests (6000.1.17f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (2023.2.22f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (2023.2.22f1)
No graphic device is available to show the window.
|
|
🧪 Run tests (2023.2.22f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (6000.4.1f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (6000.4.1f1)
No graphic device is available to show the window.
|
|
🧪 Run tests (6000.4.1f1)
No graphic device is available to initialize the view.
|
|
🧪 Run tests (6000.6.0a2)
Build failed with exit code 1
|
|
🧪 Run tests (2020.3.49f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2020.3.49f1)
Assets/TextMeshPro Support is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (2020.3.49f1)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
🧪 Run tests (2021.2.20f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2021.2.20f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2021.2.20f1)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
🧪 Run tests (2020.2.8f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2020.2.8f1)
Assets/TextMeshPro Support is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (2020.2.8f1)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
🧪 Run tests (2019.4.41f2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2019.4.41f2)
Assets/TextMeshPro Support is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (2019.4.41f2)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
🧪 Run tests (2021.1.29f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2021.1.29f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2021.1.29f1)
Assets/TextMeshPro Support is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (2021.1.29f1)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
🧪 Run tests (2020.1.18f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2020.1.18f1)
Assets/TextMeshPro Support is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (2020.1.18f1)
Assets/Samples is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (2020.1.18f1)
Library folder does not exist.
Consider setting up caching to speed up your workflow,
if this is not your first build.
|
|
🧪 Run tests (2021.3.45f2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2021.3.45f2)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2021.3.45f2)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2022.1.25f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2022.1.25f1)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2022.1.25f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2022.1.25f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2023.1.22f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2023.1.22f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2023.1.22f1)
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: Unity cannot load OpenCL.dll. Please install the latest graphics driver.
|
|
🧪 Run tests (2023.1.22f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2022.2.23f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2022.2.23f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.2.23f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2022.2.23f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2022.3.62f3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2022.3.62f3)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
GfxDevice renderer is null. Unity cannot update the Ambient Probe and Reflection Probes that the SkyManager generates. Run the Editor without the -nographics argument or generate lighting for your scene.
|
|
🧪 Run tests (2022.3.62f3)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (6000.3.13f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (6000.2.15f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (6000.2.15f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (6000.0.72f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (6000.0.72f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (6000.5.0b2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (6000.1.17f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (6000.1.17f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2023.2.22f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (2023.2.22f1)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2023.2.22f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (2023.2.22f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (2023.2.22f1)
Activation failed, attempting retry #4
|
|
🧪 Run tests (2023.2.22f1)
Activation failed, attempting retry #3
|
|
🧪 Run tests (2023.2.22f1)
Activation failed, attempting retry #2
|
|
🧪 Run tests (2023.2.22f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (6000.4.1f1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main, game-ci/unity-test-runner@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
🧪 Run tests (6000.4.1f1)
Activation failed, attempting retry #1
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/Internal/Utilities/ObjectRepository.cs(149,22): warning CS0618: 'Object.GetInstanceID()' is obsolete: 'GetInstanceID is deprecated. Use GetEntityId instead. This will be removed in a future version.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/Internal/Utilities/ObjectRepository.cs(133,24): warning CS0618: 'Object.GetInstanceID()' is obsolete: 'GetInstanceID is deprecated. Use GetEntityId instead. This will be removed in a future version.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/Internal/Utilities/Misc.cs(24,20): warning CS0618: 'Object.FindObjectsByType<T>(FindObjectsInactive, FindObjectsSortMode)' is obsolete: 'FindObjectsByType with FindObjectsSortMode parameter has been deprecated. Use FindObjectsByType<T>() or FindObjectsByType<T>(FindObjectsInactive) instead. InstanceID will be replaced in the future with EntityId and previous sort order cannot be maintained.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/Internal/Utilities/Misc.cs(24,77): warning CS0618: 'FindObjectsSortMode' is obsolete: 'FindObjectsSortMode has been deprecated. Use the FindObjectsByType overloads that do not take a FindObjectsSortMode parameter.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/SoftMask.cs(235,50): warning CS0618: 'Object.GetInstanceID()' is obsolete: 'GetInstanceID is deprecated. Use GetEntityId instead. This will be removed in a future version.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/SoftMaskable.cs(268,23): warning CS0618: 'Object.GetInstanceID()' is obsolete: 'GetInstanceID is deprecated. Use GetEntityId instead. This will be removed in a future version.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/SoftMaskable.cs(267,23): warning CS0618: 'Object.GetInstanceID()' is obsolete: 'GetInstanceID is deprecated. Use GetEntityId instead. This will be removed in a future version.'
|
|
🧪 Run tests (6000.4.1f1)
Packages/src/Runtime/MaskingShape/MaskingShapeContainer.cs(130,65): warning CS0618: 'Object.GetInstanceID()' is obsolete: 'GetInstanceID is deprecated. Use GetEntityId instead. This will be removed in a future version.'
|
|
🧪 Run tests (6000.4.1f1)
Main Object Name 'NanoMonitor' does not match filename 'NanoMonitorProjectSettings'
|
|
🧪 Run tests (6000.4.1f1)
Assets/TextMeshPro Support (Unity 6) is a symbolic link. Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing.
|
|
🧪 Run tests (6000.6.0a2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, game-ci/unity-builder@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|