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

Sign in to view logs

Triggered via pull request July 25, 2023 16:48

opened #613

release-next-ci

Status Failure

Total duration 20m 6s

Artifacts –

test-unit.yaml

on: pull_request

Matrix: Unit Test

Annotations

1 error and 3 warnings

Unit Test (1.20.2, 17, windows-latest)

Process completed with exit code 1.

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/