Skip to content

Ray Nightly0 Compatibility test #132

Ray Nightly0 Compatibility test

Ray Nightly0 Compatibility test #132

Triggered via schedule August 6, 2023 01:11
Status Failure
Total duration 9m 31s
Artifacts

ray_nightly_test.yml

on: schedule
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 9 warnings
build-and-test (ubuntu-latest, 3.7, 3.3.2)
Process completed with exit code 2.
build-and-test (ubuntu-latest, 3.7, 3.2.3)
The operation was canceled.
build-and-test (ubuntu-latest, 3.8, 3.3.2)
The operation was canceled.
build-and-test (ubuntu-latest, 3.7, 3.1.3)
The operation was canceled.
build-and-test (ubuntu-latest, 3.9, 3.1.3)
The operation was canceled.
build-and-test (ubuntu-latest, 3.9, 3.3.2)
The operation was canceled.
build-and-test (ubuntu-latest, 3.9, 3.2.3)
The operation was canceled.
build-and-test (ubuntu-latest, 3.8, 3.1.3)
The operation was canceled.
build-and-test (ubuntu-latest, 3.8, 3.2.3)
The operation was canceled.
build-and-test (ubuntu-latest, 3.7, 3.3.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.7, 3.2.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.8, 3.3.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.7, 3.1.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.9, 3.1.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.9, 3.3.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.9, 3.2.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.8, 3.1.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@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-and-test (ubuntu-latest, 3.8, 3.2.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/