Skip to content

address linting issues (#5525) #11781

address linting issues (#5525)

address linting issues (#5525) #11781

Re-run triggered November 21, 2024 16:56
Status Success
Total duration 13m 35s
Artifacts 2
Collect-Tests
3m 8s
Collect-Tests
Matrix: Static-Checks
Matrix: Build
Check-Container-Startup
1m 41s
Check-Container-Startup
Performance-Checks
2m 58s
Performance-Checks
Matrix: External-Datastores
Matrix: External-SaaS-Connectors
Matrix: Misc-Tests
Matrix: Pytest-Ctl-External
Matrix: Safe-Tests
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
Safe-Tests (3.10.13, ctl-not-external)
The job running on runner GitHub Actions 43 has exceeded the maximum execution time of 45 minutes.
Safe-Tests (3.10.13, ctl-not-external)
The operation was canceled.
Safe-Tests (3.9.18, ctl-not-external)
The job running on runner GitHub Actions 8 has exceeded the maximum execution time of 45 minutes.
Safe-Tests (3.9.18, ctl-not-external)
The operation was canceled.
Safe-Tests (3.10.13, ops-integration)
Process completed with exit code 1.
External-SaaS-Connectors (3.9.18)
The following actions use a deprecated Node.js version and will be forced to run on node20: hashicorp/vault-action@v2.5.0. For more info: https://***.blog/changelog/2024-03-07-***-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
External-SaaS-Connectors (3.10.13)
The following actions use a deprecated Node.js version and will be forced to run on node20: hashicorp/vault-action@v2.5.0. For more info: https://***.blog/changelog/2024-03-07-***-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/