Skip to content

Add a flag to cancel immediately instead of player loop #540

Add a flag to cancel immediately instead of player loop

Add a flag to cancel immediately instead of player loop #540

Triggered via pull request October 27, 2023 11:12
Status Failure
Total duration 7m 16s
Artifacts 3

build-debug.yml

on: pull_request
build-dotnet
59s
build-dotnet
Matrix: build-unity
Fit to window
Zoom out
Zoom in

Annotations

1 error and 12 warnings
build-dotnet
Process completed with exit code 1.
build-dotnet
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-dotnet
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-dotnet
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-dotnet
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-dotnet: src/UniTask.NetCoreTests/TaskExtensionsTest.cs#L38
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-dotnet: src/UniTask.NetCoreTests/Linq/Merge.cs#L102
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-unity (2019.3.9f1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
build-unity (2019.3.9f1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-unity (2019.4.13f1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
build-unity (2019.4.13f1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-unity (2020.1.12f1)
Library folder does not exist. Consider setting up caching to speed up your workflow, if this is not your first build.
build-unity (2020.1.12f1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
UniTask.unitypackage-2019.3.9f1.zip Expired
192 KB
UniTask.unitypackage-2019.4.13f1.zip Expired
192 KB
UniTask.unitypackage-2020.1.12f1.zip Expired
192 KB