Skip to content

Multi-Processing Functionality for create-workload #336

Multi-Processing Functionality for create-workload

Multi-Processing Functionality for create-workload #336

Triggered via pull request November 1, 2023 21:29
Status Failure
Total duration 28m 3s
Artifacts

manual-integ.yml

on: pull_request
Matrix: Integration-Tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Integration-Tests (3.9)
Process completed with exit code 2.
Integration-Tests (3.10)
The operation was canceled.
Integration-Tests (3.11)
The operation was canceled.
Integration-Tests (3.8)
The operation was canceled.
Integration-Tests (3.9)
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/
Integration-Tests (3.10)
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/
Integration-Tests (3.11)
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/
Integration-Tests (3.8)
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/