Skip to content

🤖 triggering CI on branch 'release-next' after synching from upstream/main #879

🤖 triggering CI on branch 'release-next' after synching from upstream/main

🤖 triggering CI on branch 'release-next' after synching from upstream/main #879

Triggered via pull request December 19, 2023 00:42
Status Failure
Total duration 13m 58s
Artifacts

test-unit.yaml

on: pull_request
Matrix: Unit Test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Unit Test (17, ubuntu-latest)
Process completed with exit code 2.
Unit Test (17, windows-latest)
The operation was canceled.
Unit Test (17, macos-latest)
The operation was canceled.
Unit Test (17, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit Test (17, windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit Test (17, macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/