Skip to content

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

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

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

Triggered via pull request September 11, 2023 13:46
Status Success
Total duration 31m 42s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

test-unit.yaml

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

Annotations

3 warnings
Unit Test (1.20.2, 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 (1.20.2, 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/
Unit Test (1.20.2, 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/