Trigger Reference generation (dispatch) #3
trigger-generate-reference.yml
on: workflow_dispatch
call-generate-reference
/
release
7s
Matrix: call-generate-reference / generation
Annotations
52 errors and 13 warnings
|
call-generate-reference / generation (valid-v830, windows-2022)
Process completed with exit code 1.
|
|
call-generate-reference / generation (valid-mps, windows-2022)
Process completed with exit code 1.
|
|
call-generate-reference / generation (valid-thermal, windows-2022)
Process completed with exit code 1.
|
|
call-generate-reference / generation (valid-filter-outputs, windows-2022)
Process completed with exit code 1.
|
|
call-generate-reference / generation (long-tests-1, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (short-tests, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (medium-tests, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (long-tests-3, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-adq, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (long-tests-1, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (short-tests, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-hydroBind, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-bind, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-bind, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-adq, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-complex, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (medium-tests, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-defaillance, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-hydro, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-filter-outputs, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (long-tests-2, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-parallel, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-hydroPricing, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-ts-gen-export, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-hydroBind, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-v860, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (adequacy-patch-CSR, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-parallel, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-thermal, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-hydro, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-hydroPricing, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-ts-gen-export, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-v830, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-v870, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-v860, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-milp, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-milp, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-named-mps, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-v870, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-named-mps, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (long-tests-3, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (long-tests-3, windows-2022)
The operation was canceled.
|
|
call-generate-reference / generation (valid-marginCost, windows-2022)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-marginCost, windows-2022)
The operation was canceled.
|
|
call-generate-reference / generation (valid-defaillance, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-defaillance, ubuntu-22.04)
The operation was canceled.
|
|
call-generate-reference / generation (long-tests-2, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (long-tests-2, ubuntu-22.04)
The operation was canceled.
|
|
call-generate-reference / generation (valid-complex, ubuntu-22.04)
The run was canceled by @payetvin.
|
|
call-generate-reference / generation (valid-complex, ubuntu-22.04)
The operation was canceled.
|
|
Trigger Reference generation (dispatch)
The run was canceled by @payetvin.
|
|
Trigger Reference generation (dispatch)
The run was canceled by @payetvin.
|
|
call-generate-reference / release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-v830, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-mps, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (adequacy-patch-CSR, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-marginCost, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-thermal, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-filter-outputs, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-mps, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (long-tests-3, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-marginCost, windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-defaillance, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (long-tests-2, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
call-generate-reference / generation (valid-complex, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|