Skip to content

Change build notification to say development not nightly #104

Change build notification to say development not nightly

Change build notification to say development not nightly #104

Triggered via push November 17, 2024 04:09
Status Success
Total duration 37m 59s
Artifacts 4

build.yml

on: push
Matrix: buildForAllSupportedPlatforms
sendSuccessNotification
4s
sendSuccessNotification
sendFailureNotification
0s
sendFailureNotification
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 30 warnings
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for StandaloneLinux64
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for Android
ArgumentNullException: Value cannot be null.
Build for StandaloneWindows64
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build for StandaloneWindows64
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build for StandaloneWindows64
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for StandaloneWindows64
Assets/MaterialLibrary/HexagonSpread/HexagonTransition.cs(141,22): warning CS0414: The field 'HexagonTransition._init' is assigned but its value is never used
Build for StandaloneWindows64
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for StandaloneWindows64
[ServicesCore]: To use Unity's dashboard services, you need to link your Unity project to a project ID. To do this, go to Project Settings to select your organization, select your project and then link a project ID. You also need to make sure your organization has access to the required products. Visit https://dashboard.unity3d.com to sign up.
Build for StandaloneWindows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build for StandaloneWindows
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build for StandaloneWindows
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for StandaloneWindows
Assets/MaterialLibrary/HexagonSpread/HexagonTransition.cs(141,22): warning CS0414: The field 'HexagonTransition._init' is assigned but its value is never used
Build for StandaloneWindows
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for StandaloneWindows
[ServicesCore]: To use Unity's dashboard services, you need to link your Unity project to a project ID. To do this, go to Project Settings to select your organization, select your project and then link a project ID. You also need to make sure your organization has access to the required products. Visit https://dashboard.unity3d.com to sign up.
Build for StandaloneLinux64
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build for StandaloneLinux64
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build for StandaloneLinux64
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for StandaloneLinux64
Assets/MaterialLibrary/HexagonSpread/HexagonTransition.cs(141,22): warning CS0414: The field 'HexagonTransition._init' is assigned but its value is never used
Build for StandaloneLinux64
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for StandaloneLinux64
[ServicesCore]: To use Unity's dashboard services, you need to link your Unity project to a project ID. To do this, go to Project Settings to select your organization, select your project and then link a project ID. You also need to make sure your organization has access to the required products. Visit https://dashboard.unity3d.com to sign up.
Build for Android
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build for Android
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
Build for Android
Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance
Build for Android
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
Build for Android
[Worker0] Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance
Build for Android
[Worker0] To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
Build for Android
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for Android
Built In Data does not have any associated AddressableAssetGroupSchemas. Data from this group will not be included in the build. If this is unexpected the AddressableGroup may have become corrupted.
Build for Android
[ServicesCore]: To use Unity's dashboard services, you need to link your Unity project to a project ID. To do this, go to Project Settings to select your organization, select your project and then link a project ID. You also need to make sure your organization has access to the required products. Visit https://dashboard.unity3d.com to sign up.
Build for Android
Errors during XML parse:
Build for Android
Additionally, the fallback loader failed to parse the XML.
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "Android", "StandaloneLinux64", "StandaloneWindows", "StandaloneWindows64". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
Android
71.8 MB
StandaloneLinux64
188 MB
StandaloneWindows
174 MB
StandaloneWindows64
186 MB