Fix main build #1320
SovietacedAnnotations
27 errors and 9 warnings
|
test (manager)
Process completed with exit code 1.
|
|
test (manager):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytecopilot)
Process completed with exit code 1.
|
|
test (flytecopilot):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytecopilot):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (dataproxy)
Process completed with exit code 1.
|
|
test (dataproxy):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (dataproxy):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (actions)
Process completed with exit code 1.
|
|
test (actions):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (actions):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (executor)
Process completed with exit code 1.
|
|
test (executor):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (executor):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytestdlib)
Process completed with exit code 1.
|
|
test (flytestdlib):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytestdlib):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytestdlib):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytestdlib):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flytestdlib):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (runs)
Process completed with exit code 1.
|
|
test (runs):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (runs):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (runs):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flyteplugins)
Process completed with exit code 1.
|
|
test (flyteplugins):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (flyteplugins):
flytestdlib/config/viper/collection.go#L12
missing go.sum entry for module providing package github.com/spf13/viper (imported by github.com/flyteorg/flyte/v2/flytestdlib/config/viper); to add:
|
|
test (manager)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (flyteidl2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (flytecopilot)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (dataproxy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (actions)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (executor)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (flytestdlib)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (runs)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
|
test (flyteplugins)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
coverage-actions
Expired
|
3.94 KB |
sha256:d60e487b734f777be992bcda07345ba3fe5664530cbcc4b911bb37060ba3378b
|
|
|
coverage-dataproxy
Expired
|
6.18 KB |
sha256:89e1cc5804f487d6b69ab65cb9419d50df3eeec0c0d8c6e1dd4d91336bed2819
|
|
|
coverage-executor
Expired
|
7.11 KB |
sha256:dddbcbac270ab0d67adc0f20a644fa7d89c15e19ffbc5f2306e080ba421d4700
|
|
|
coverage-flytecopilot
Expired
|
2.34 KB |
sha256:d4b4621985bac13e36f98a3bc3d6d51d21efc729e0ee77928a8eee779c56c671
|
|
|
coverage-flyteidl2
Expired
|
1.88 KB |
sha256:17121e98f3fab04c3e097eef72a6f3087511baaaca19c17b0962c409bedb8dfe
|
|
|
coverage-flyteplugins
Expired
|
49.7 KB |
sha256:c0f566cf8ee1bf4022379aab4dc593388d024b3ae54360e4bb0cd52db473d5f4
|
|
|
coverage-flytestdlib
Expired
|
84.5 KB |
sha256:215b3d37866926136638e6a392bf4ca8271c0ade34f201cb2b97b2cfa7d968e6
|
|
|
coverage-manager
Expired
|
710 Bytes |
sha256:6757bcb1fa8d35d323ecccc7e7c15d185ac6154b3e99c93e2aecf25f01a7ded4
|
|
|
coverage-runs
Expired
|
23.4 KB |
sha256:7d027189ba365dd3b8fcef9f21f4ee466224df3df37ec4f71d93a31c9c1e579f
|
|