Skip to content

reserialize assets #135

reserialize assets

reserialize assets #135

Triggered via push April 26, 2025 04:05
Status Failure
Total duration 10m 21s
Artifacts 2
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

29 errors and 12 warnings
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2020.3.48f1
Build failed with exit code 1
Build-StandaloneWindows-2019.4.40f1
Build failed with exit code 1
Build-StandaloneWindows-2019.4.40f1
Scripts have compiler errors.
Build-StandaloneWindows-2021.3.45f1
Build failed with exit code 1
Build-StandaloneWindows-2022.3.43f1
Build failed with exit code 1
Build-StandaloneWindows-2019.3.15f1
Build failed with exit code 1
Build-StandaloneWindows-2019.3.15f1
Scripts have compiler errors.
Build-WebGL-2019.3.15f1
Build failed with exit code 1
Build-WebGL-2019.3.15f1
Scripts have compiler errors.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_2D_platformer_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/TestEntityImportInterface/TestEntityImportInterface/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Entities/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFieldsLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/Test_file_for_API_showing_all_featuresLevels/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/WorldMap_Free_layout/NuclearBlaze_by_deepnight.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/Typical_TopDown_example/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Samples/Samples/AutoLayers_5_Advanced/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-WebGL-6000.0.23f1
<color=#FFCC00>LDtk:</color> Loading artifacts didn't work for getting tileset sprite artifacts. You should investigate the tileset file at "Assets/Tests/Misc/OtherTechTests/TestAllFields/Internal_Icons.ldtkt". Find that tileset file, select it, and click "Print to Console" to see the actual issue with it.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:Transform'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:GameObject'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:Transform'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:GameObject'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:GameObject'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:Transform'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:GameObject'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:GameObject'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:Transform'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.4.40f1
Identifier uniqueness violation: 'Name:Missing Prefab (Dummy), Type:GameObject'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets.
Build-StandaloneWindows-2019.3.15f1
Activation failed, attempting retry #1
Build-WebGL-2019.3.15f1
Activation failed, attempting retry #1

Artifacts

Produced during runtime
Name Size Digest
Build-StandaloneWindows-6000.0.23f1 Expired
25.8 MB
sha256:5b79141c59c105eb786940638d15f472dad0fccf9f98af1056c24fd3aaa1bc5e
Build-WebGL-6000.0.23f1 Expired
3.92 MB
sha256:1aa53e5961a10600813d18c79fd23313f94a58034fb1351e38ae3cacfd8092c1