Driver launcher hooks mlflow #4
alyssacgoinsintegration-tests-v1.yml
on: pull_request
Matrix: build / image-build
Matrix: initialization-integration-tests-v1
Annotations
20 errors and 8 warnings
|
build / image-build (viewer-crd-controller, backend/Dockerfile.viewercontroller, .)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c GO111MODULE=on go build -o /bin/controller backend/src/crd/controller/viewer/*.go" did not complete successfully: exit code: 1
|
|
build / image-build (launcher, backend/Dockerfile.launcher, .)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c GO111MODULE=on CGO_ENABLED=0 GOOS=linux go build -tags netgo -ldflags '-extldflags \"-static\"' -o /bin/launcher-v2 ./backend/src/v2/cmd/launcher-v2/*.go" did not complete successfully: exit code: 1
|
|
build / image-build (cache-deployer, backend/src/cache/deployer/Dockerfile, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (visualization-server, backend/Dockerfile.visualization, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (persistenceagent, backend/Dockerfile.persistenceagent, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (persistenceagent, backend/Dockerfile.persistenceagent, .)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c GO111MODULE=on go build -o /bin/persistence_agent backend/src/agent/persistence/*.go" did not complete successfully: exit code: 1
|
|
build / image-build (metadata-envoy, third_party/metadata_envoy/Dockerfile, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (metadata-envoy, third_party/metadata_envoy/Dockerfile, .)
The operation was canceled.
|
|
build / image-build (cache-server, backend/Dockerfile.cacheserver, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (cache-server, backend/Dockerfile.cacheserver, .)
The operation was canceled.
|
|
build / image-build (scheduledworkflow, backend/Dockerfile.scheduledworkflow, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (scheduledworkflow, backend/Dockerfile.scheduledworkflow, .)
A task was canceled.
|
|
build / image-build (driver, backend/Dockerfile.driver, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (driver, backend/Dockerfile.driver, .)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c GO111MODULE=on CGO_ENABLED=0 GOOS=linux go build -tags netgo -gcflags=\"${GCFLAGS}\" -ldflags '-extldflags \"-static\"' -o /bin/driver ./backend/src/v2/cmd/driver/*.go" did not complete successfully: exit code: 1
|
|
build / image-build (metadata-writer, backend/metadata_writer/Dockerfile, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (metadata-writer, backend/metadata_writer/Dockerfile, .)
The operation was canceled.
|
|
build / image-build (apiserver, backend/Dockerfile, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (apiserver, backend/Dockerfile, .)
The operation was canceled.
|
|
build / image-build (frontend, frontend/Dockerfile, .)
The strategy configuration was canceled because "build.image-build.viewer-crd-controller_bac" failed
|
|
build / image-build (frontend, frontend/Dockerfile, .)
The operation was canceled.
|
|
build / image-build (viewer-crd-controller, backend/Dockerfile.viewercontroller, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / image-build (launcher, backend/Dockerfile.launcher, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / image-build (persistenceagent, backend/Dockerfile.persistenceagent, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / image-build (driver, backend/Dockerfile.driver, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / image-build (metadata-writer, backend/metadata_writer/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
backend/metadata_writer/Dockerfile#L6
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
build / image-build (apiserver, backend/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / image-build (frontend, frontend/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|