unity-test

unity-test #246

Triggered via schedule June 16, 2024 00:58

mob-sakai

⁠ 7b73d99

main

Status Failure

Total duration 6m 28s

Artifacts –

unity-test.yml

on: schedule

setup

Matrix: test

Annotations

34 errors and 35 warnings

test (2023.1.20f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2023.1.20f1)

The process '/usr/bin/docker' failed with exit code 1

test (2023.3.0b10)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2023.3.0b10)

The process '/usr/bin/docker' failed with exit code 1

test (6000.0.5f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (6000.0.5f1)

The process '/usr/bin/docker' failed with exit code 1

test (2023.2.20f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2023.2.20f1)

The process '/usr/bin/docker' failed with exit code 1

test (2022.1.24f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2022.1.24f1)

The process '/usr/bin/docker' failed with exit code 1

test (2022.3.33f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2022.3.33f1)

The process '/usr/bin/docker' failed with exit code 1

test (2022.2.21f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2022.2.21f1)

The process '/usr/bin/docker' failed with exit code 1

test (2021.3.39f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2021.3.39f1)

The process '/usr/bin/docker' failed with exit code 1

test (2021.1.28f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2021.1.28f1)

The process '/usr/bin/docker' failed with exit code 1

test (2020.3.48f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2020.3.48f1)

The process '/usr/bin/docker' failed with exit code 1

test (2020.2.7f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2020.2.7f1)

The process '/usr/bin/docker' failed with exit code 1

test (2021.2.19f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2021.2.19f1)

The process '/usr/bin/docker' failed with exit code 1

test (2020.1.17f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2020.1.17f1)

The process '/usr/bin/docker' failed with exit code 1

test (2019.1.14f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2019.1.14f1)

The process '/usr/bin/docker' failed with exit code 1

test (2019.4.40f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2019.4.40f1)

The process '/usr/bin/docker' failed with exit code 1

test (2019.3.15f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2019.3.15f1)

The process '/usr/bin/docker' failed with exit code 1

test (2018.4.36f1)

No valid license activation strategy could be determined. Make sure to provide UNITY_EMAIL, UNITY_PASSWORD, and either a UNITY_SERIAL or UNITY_LICENSE. Otherwise please use UNITY_LICENSING_SERVER.

test (2018.4.36f1)

The process '/usr/bin/docker' failed with exit code 1

setup

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

test (2023.1.20f1)

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

test (2023.1.20f1)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

test (2023.3.0b10)