add utility to setup configuration at the beginning of the tests #9111
SylvainSenechalend2end.yaml
on: push
build-kafka
26s
check-dashboard-versions
41s
create-deployments
6s
check-alerts
/
run-alert-tests
29s
check-scripts
10s
check-workflows
3m 52s
build-doc
3m 8s
lint-functional-tests
2m 41s
check-mongo-patches
12s
end2end-pra
2m 45s
end2end-2-shards-http
2m 38s
end2end-sharded
2m 41s
ctst-end2end-sharded
2m 40s
write-final-status
update-deployments
7s
Annotations
26 errors, 34 warnings, and 8 notices
|
lint-functional-tests
Process completed with exit code 1.
|
|
lint-functional-tests:
tests/functional/ctst/common/hooks.ts#L26
Unexpected console statement
|
|
end2end-2-shards-http
Process completed with exit code 1.
|
|
end2end-2-shards-http
Process completed with exit code 1.
|
|
end2end-2-shards-http
❌ No test results found for end2end-2-shards-http.3
|
|
end2end-2-shards-http
Process completed with exit code 1.
|
|
end2end-2-shards-http
Usage: .github/scripts/merge-junit-reports.py <output.xml> <input1.xml> ...
|
|
end2end-2-shards-http
Process completed with exit code 128.
|
|
end2end-pra
Process completed with exit code 1.
|
|
end2end-pra
Process completed with exit code 1.
|
|
end2end-pra
❌ No test results found for end2end-pra.3
|
|
end2end-pra
Process completed with exit code 1.
|
|
end2end-pra
Usage: .github/scripts/merge-junit-reports.py <output.xml> <input1.xml> ...
|
|
end2end-pra
Process completed with exit code 128.
|
|
ctst-end2end-sharded
Process completed with exit code 1.
|
|
ctst-end2end-sharded
Process completed with exit code 1.
|
|
ctst-end2end-sharded
❌ No test results found for ctst-end2end-sharded.3
|
|
ctst-end2end-sharded
Process completed with exit code 1.
|
|
ctst-end2end-sharded
Usage: .github/scripts/merge-junit-reports.py <output.xml> <input1.xml> ...
|
|
ctst-end2end-sharded
Process completed with exit code 128.
|
|
end2end-sharded
Process completed with exit code 1.
|
|
end2end-sharded
Process completed with exit code 1.
|
|
end2end-sharded
❌ No test results found for end2end-sharded.3
|
|
end2end-sharded
Process completed with exit code 1.
|
|
end2end-sharded
Usage: .github/scripts/merge-junit-reports.py <output.xml> <input1.xml> ...
|
|
end2end-sharded
Process completed with exit code 128.
|
|
create-deployments
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
|
|
check-scripts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. 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/
|
|
check-alerts / run-alert-tests
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
check-alerts / run-alert-tests
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
lint-functional-tests
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
lint-functional-tests
Unexpected parentheses around single function argument
|
|
lint-functional-tests
Unexpected parentheses around single function argument
|
|
lint-functional-tests:
tests/functional/mocha/backbeat/LifecycleUtility.js#L135
Unexpected parentheses around single function argument
|
|
lint-functional-tests
Unexpected parentheses around single function argument
|
|
lint-functional-tests:
tests/functional/mocha/backbeat/IngestionUtility.js#L29
Unexpected parentheses around single function argument
|
|
lint-functional-tests
'host' is never reassigned. Use 'const' instead
|
|
lint-functional-tests:
tests/functional/ctst/steps/azureArchive.ts#L414
Unexpected function expression
|
|
lint-functional-tests:
tests/functional/ctst/steps/azureArchive.ts#L381
Unexpected function expression
|
|
lint-functional-tests:
tests/functional/ctst/common/hooks.ts#L26
Strings must use singlequote
|
|
lint-functional-tests:
tests/functional/ctst/common/hooks.ts#L22
Unexpected function expression
|
|
lint-functional-tests
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
build-doc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
end2end-2-shards-http
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
end2end-2-shards-http
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
end2end-2-shards-http
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
end2end-pra
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
end2end-pra
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
end2end-pra
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
check-workflows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
ctst-end2end-sharded
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
ctst-end2end-sharded
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
ctst-end2end-sharded
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
end2end-sharded
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
end2end-sharded
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
end2end-sharded
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
build-iso
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@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/
|
|
build-iso
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
build-iso
Input 'app-id' has been deprecated with message: Use 'client-id' instead.
|
|
update-deployments
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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-doc
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
end2end-2-shards-http
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
end2end-pra
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
check-workflows
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
ctst-end2end-sharded
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
end2end-sharded
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
build-iso
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
|
build-iso
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:Zenko:staging-0ddc9e703c.build-iso-and-end2end-test.9111
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
scality~Zenko~HWT06F.dockerbuild
|
45.4 KB |
sha256:2172d377269a6313d6f989a5a21aadf5b62e1a15016c5bc167d44979ec6a4dfd
|
|
|
scality~Zenko~MZGDG7.dockerbuild
|
40 KB |
sha256:ea37e677552727dbd9767d7bd7a20d643f9d6cd4f7706c42a0a5c0278f071c6a
|
|