Gerrit Composed Maven Verify #2708
gerrit-verify.yaml
on: workflow_dispatch
prepare
15s
info-yaml-verify
/
prepare
15s
Matrix: tox-verify / run-tox
maven-verify
/
maven-verify
26m 12s
pre-commit-linting
/
actionlint
8s
pre-commit-linting
/
pre-commit
35s
vote
9s
info-yaml-verify
/
vote
7s
Annotations
4 errors and 6 warnings
|
tox-verify / run-tox (docs-linkcheck)
Process completed with exit code 1.
|
|
tox-verify / run-tox (docs)
The strategy configuration was canceled because "tox-verify.run-tox.docs-linkcheck" failed
|
|
tox-verify / run-tox (docs)
The operation was canceled.
|
|
maven-verify / maven-verify
Could not start JMX connector server
|
|
info-yaml-verify / prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4. 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/
|
|
prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4. 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/
|
|
info-yaml-verify / info-validation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11. 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/
|
|
info-yaml-verify / vote
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: im-open/workflow-conclusion@e4f7c4980600fbe0818173e30931d3550801b992, shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4. 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/
|
|
maven-verify / maven-verify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, infovista-opensource/vars-to-env-action@3d3e7c8ae1e9e5fcd9ce83e56ab85a6a135d2ffa, stCarolas/setup-maven@d6af6abeda15e98926a57b5aa970a96bb37f97d1. 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/
|
|
vote
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: im-open/workflow-conclusion@e4f7c4980600fbe0818173e30931d3550801b992, shimataro/ssh-key-action@d4fffb50872869abe2d9a9098a6d9c5aa7d16be4. 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/
|