fixup! fixup! fixup! Separate reporting vs build status steps #8742
end2end.yaml
on: push
build-kafka
1m 20s
check-dashboard-versions
21s
build-test-image
2m 19s
lint-and-build-ctst
8m 9s
check-alerts
/
run-alert-tests
44s
check-workflows
2m 36s
build-doc
3m 8s
check-mongo-patches
12s
write-final-status
7s
Annotations
9 errors, 3 warnings, and 3 notices
|
DMF.Deletion of a restored object:
DMF#L1
function timed out, ensure the promise resolves within 130000 milliseconds
|
|
Live Object Replication.Object of 4 MiB (above threshold, stripped) replicates with location stripping threshold:
Live Object Replication#L1
Timeout: Object 'repl-strip-obj-1' is still in pending/processing state after timeout
|
|
Live Object Replication.Object of 2 MiB (at threshold, stripped) replicates with location stripping threshold:
Live Object Replication#L1
Timeout: Object 'repl-strip-obj-1' is still in pending/processing state after timeout
|
|
Live Object Replication.Object of 1 MiB (below threshold) replicates with location stripping threshold:
Live Object Replication#L1
Timeout: Object 'repl-strip-obj-1' is still in pending/processing state after timeout
|
|
Live Object Replication.Object of 0 bytes (zero-byte) replicates with location stripping threshold:
Live Object Replication#L1
Timeout: Object 'repl-strip-obj-1' is still in pending/processing state after timeout
|
|
Replication.Re-replicate objects that failed to replicate:
Replication#L1
Timeout: Object 'source-object-2' is still in pending/processing state after timeout
|
|
Replication.Replicate objects created before creating the replication rule:
Replication#L1
Timeout: Object 'source-object-1' is still in pending/processing state after timeout
|
|
Kafka Cleaner.Verify that consumed messages gets deleted by kafkacleaner:
Kafka Cleaner#L1
Kafka cleaner did not clean the topics within the expected time
|
|
ctst-end2end-sharded
Process completed with exit code 1.
|
|
ctst-end2end-sharded
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-github-app-token@v2, Azure/setup-kubectl@v4, scality/action-artifacts@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ctst-end2end-sharded
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
write-final-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
ctst-end2end-sharded
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-1c7ac58653.build-iso-and-end2end-test.8742
|
|
Banzaicloud Charts not available:
install-kind-dependencies.sh#L51
Failed to add banzaicloud-stable repo, using local checkout
|
|
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-1c7ac58653.build-iso-and-end2end-test.8742
|