chore: bump azure/setup-helm from 4.2.0 to 4.3.0 #1596
Triggered via pull request
February 18, 2025 10:14
dependabot[bot]
Status
Failure
Total duration
10m 16s
Artifacts
–
flow-pull-request-checks.yaml
on: pull_request
Code
/
Compiles
1m 24s
Unit Tests
/
Standard
2m 36s
E2E Tests
/
Standard
9m 28s
Sonar Analysis
/
Standard
1m 22s
Annotations
6 warnings
|
Code / Compiles
Cache not found for keys: node-cache-Linux-x64-npm-72e8ab5f3d97880834831304eb6600bef9f475e3a35fb0cf4b6b29b0f1bdaa58
|
|
Sonar Analysis / Standard
Cache not found for keys: node-cache-Linux-x64-npm-72e8ab5f3d97880834831304eb6600bef9f475e3a35fb0cf4b6b29b0f1bdaa58
|
|
Unit Tests / Standard
Cache not found for keys: node-cache-Linux-x64-npm-72e8ab5f3d97880834831304eb6600bef9f475e3a35fb0cf4b6b29b0f1bdaa58
|
|
Unit Tests / Standard
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests / Standard
Cache not found for keys: node-cache-Linux-x64-npm-72e8ab5f3d97880834831304eb6600bef9f475e3a35fb0cf4b6b29b0f1bdaa58
|
|
E2E Tests / Standard
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|