Skip to content

Validate stacks

Validate stacks #3670

Triggered via schedule July 20, 2026 06:00
Status Cancelled
Total duration 6h 0m 45s
Artifacts

validate-stacks.yaml

on: schedule
validate devfile schemas
1m 12s
validate devfile schemas
check for non-terminating images
1h 27m
check for non-terminating images
with odo v2
6h 0m
with odo v2
with odo v3
0s
with odo v3
send slack notification
0s
send slack notification
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
with odo v2
The job has exceeded the maximum execution time of 6h0m0s
with odo v2
The operation was canceled.
validate devfile schemas
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@3041bf56c941b39c61721a86cd11f3bb1338122a. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
validate devfile schemas
Restore cache failed: Dependencies file is not found in /home/runner/work/registry/registry. Supported file pattern: go.sum
check for non-terminating images
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, manusa/actions-setup-minikube@0e8062ceff873bd77979f39cf8fd3621416afe4d. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
with odo v2
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, manusa/actions-setup-minikube@0e8062ceff873bd77979f39cf8fd3621416afe4d, redhat-actions/openshift-tools-installer@144527c7d98999f2652264c048c7a9bd103f8a82. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
with odo v2
Failed to cache odo v2.5.1: ReserveCacheError: Unable to reserve cache with key odo_v2.5.1_linux_amd64, another job may be creating this cache.
with odo v2
Failed to check cache for odo v2.5.1: Error: Cache service responded with 400