Skip to content

CI/CD

CI/CD #134

Triggered via schedule November 23, 2023 21:03
Status Cancelled
Total duration 50s
Artifacts

CICD.yml

on: schedule
Matrix: build_and_test
Matrix: upload_results / upload_results
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 7 warnings
build_and_test (Release, windows-2022, none) / build
Process completed with exit code 1.
build_and_test (Release, windows-2022, jit) / build
The operation was canceled.
build_and_test (Debug, windows-2022, jit) / build
The operation was canceled.
build_and_test (Debug, windows-2019, jit) / build
The operation was canceled.
build_and_test (Debug, windows-2022, none) / build
The operation was canceled.
build_and_test (Debug, windows-2019, none) / build
The operation was canceled.
build_and_test (Release, windows-2019, none) / build
The operation was canceled.
build_and_test (Release, windows-2019, jit) / build
The operation was canceled.
build_and_test (Debug, ubuntu-22.04, sanitizer) / build
FailFast: cancelling since parallel instance has failed
build_and_test (Debug, ubuntu-22.04, sanitizer) / build
The operation was canceled.
build_and_test (Debug, ubuntu-22.04, coverage) / build
FailFast: cancelling since parallel instance has failed
build_and_test (Debug, ubuntu-22.04, coverage) / build
The operation was canceled.
build_and_test (Release, ubuntu-22.04, none) / build
FailFast: cancelling since parallel instance has failed
build_and_test (Release, ubuntu-22.04, none) / build
The operation was canceled.
build_and_test (Debug, ubuntu-22.04, none) / build
FailFast: cancelling since parallel instance has failed
build_and_test (Debug, ubuntu-22.04, none) / build
The operation was canceled.
build_and_test (Release, ubuntu-22.04, coverage) / build
FailFast: cancelling since parallel instance has failed
build_and_test (Release, ubuntu-22.04, coverage) / build
The operation was canceled.
build_and_test (Release, ubuntu-22.04, sanitizer) / build
FailFast: cancelling since parallel instance has failed
build_and_test (Release, ubuntu-22.04, sanitizer) / build
The operation was canceled.
build_and_test (Release, windows-2022, jit) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 (Debug, windows-2022, jit) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 (Debug, windows-2019, jit) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 (Debug, windows-2022, none) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 (Debug, windows-2019, none) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 (Release, windows-2019, none) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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 (Release, windows-2019, jit) / build
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/