Skip to content

feat: Use informer cache in ISBService rollout controller #1034

feat: Use informer cache in ISBService rollout controller

feat: Use informer cache in ISBService rollout controller #1034

Triggered via pull request October 9, 2024 17:00
Status Failure
Total duration 8m 38s
Artifacts 3

ci.yaml

on: pull_request
Matrix: E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Unit Tests
Process completed with exit code 2.
E2E Tests (true)
Process completed with exit code 2.
Codegen
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Unit Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
E2E Tests (true)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
E2E Tests (false)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
controller-logs-false
60.3 KB
controller-logs-true
7.2 KB
resource-changes-true
16 KB