Skip to content

ID-45: Session CLI and Scripted Execution #26

ID-45: Session CLI and Scripted Execution

ID-45: Session CLI and Scripted Execution #26

Triggered via pull request April 7, 2026 01:54
Status Failure
Total duration 24s
Artifacts 15
find-execution-scripts
3s
find-execution-scripts
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

30 errors and 16 warnings
test (execution_scripts/auth_info/auth_info_suite_with_preset.yaml)
Process completed with exit code 1.
test (execution_scripts/auth_info/auth_info_suite_with_preset.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/paired_suites/suite_a_against_suite_b_with_commands.yaml)
Process completed with exit code 1.
test (execution_scripts/paired_suites/suite_a_against_suite_b_with_commands.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/demo/demo_individual_tests.yaml)
Process completed with exit code 1.
test (execution_scripts/demo/demo_individual_tests.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/validator/validator_suite_alternate_expected_file.yaml)
Process completed with exit code 1.
test (execution_scripts/validator/validator_suite_alternate_expected_file.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/validator/validator_suite_with_file_input.yaml)
Process completed with exit code 1.
test (execution_scripts/validator/validator_suite_with_file_input.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/auth_info/auth_info_suite.yaml)
Process completed with exit code 1.
test (execution_scripts/auth_info/auth_info_suite.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/options/options_suite_v2_option3.yaml)
Process completed with exit code 1.
test (execution_scripts/options/options_suite_v2_option3.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/demo/demo_wait_group_cancel_failure.yaml)
Process completed with exit code 1.
test (execution_scripts/demo/demo_wait_group_cancel_failure.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/infrastructure/infrastructure_suite.yaml)
Process completed with exit code 1.
test (execution_scripts/infrastructure/infrastructure_suite.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/demo/demo_wait_group_with_commands.yaml)
Process completed with exit code 1.
test (execution_scripts/demo/demo_wait_group_with_commands.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/auth_info/auth_info_input_as_hash.yaml)
Process completed with exit code 1.
test (execution_scripts/auth_info/auth_info_input_as_hash.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/demo/demo_wait_group_unexpected_commands_failure.yaml)
Process completed with exit code 1.
test (execution_scripts/demo/demo_wait_group_unexpected_commands_failure.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/options/options_suite_v1_option1.yaml)
Process completed with exit code 1.
test (execution_scripts/options/options_suite_v1_option1.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/custom_results/custom_results_suite.yaml)
Process completed with exit code 1.
test (execution_scripts/custom_results/custom_results_suite.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
test (execution_scripts/demo/demo_wait_group_loop_with_commands_failure.yaml)
Process completed with exit code 1.
test (execution_scripts/demo/demo_wait_group_loop_with_commands_failure.yaml)
The process '/opt/hostedtoolcache/Ruby/3.3.6/x64/bin/bundle' failed with exit code 16
find-execution-scripts
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. 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 (execution_scripts/auth_info/auth_info_suite_with_preset.yaml)
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/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 (execution_scripts/paired_suites/suite_a_against_suite_b_with_commands.yaml)
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/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 (execution_scripts/demo/demo_individual_tests.yaml)
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/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 (execution_scripts/validator/validator_suite_alternate_expected_file.yaml)
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/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 (execution_scripts/validator/validator_suite_with_file_input.yaml)
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/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 (execution_scripts/auth_info/auth_info_suite.yaml)
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/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 (execution_scripts/options/options_suite_v2_option3.yaml)
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/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 (execution_scripts/demo/demo_wait_group_cancel_failure.yaml)
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/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 (execution_scripts/infrastructure/infrastructure_suite.yaml)
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/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 (execution_scripts/demo/demo_wait_group_with_commands.yaml)
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/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 (execution_scripts/auth_info/auth_info_input_as_hash.yaml)
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/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 (execution_scripts/demo/demo_wait_group_unexpected_commands_failure.yaml)
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/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 (execution_scripts/options/options_suite_v1_option1.yaml)
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/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 (execution_scripts/custom_results/custom_results_suite.yaml)
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/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 (execution_scripts/demo/demo_wait_group_loop_with_commands_failure.yaml)
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/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
debug-auth_info_input_as_hash
1.9 KB
sha256:1237e26b0a0e853692acf7c74a1087c349fde7542f16d2129e214ea52e2085e3
debug-auth_info_suite
1.9 KB
sha256:1237e26b0a0e853692acf7c74a1087c349fde7542f16d2129e214ea52e2085e3
debug-auth_info_suite_with_preset
1.9 KB
sha256:16a64fd3607a5b2ec1d4becf916cd37959ae431acbd4fa3085cec00ea9ca2263
debug-custom_results_suite
1.9 KB
sha256:3a60796b5872cc4f3d239dcd6c60e82b3184cdc31b6b415b9fbd4a875353fab8
debug-demo_individual_tests
1.9 KB
sha256:a6fb3688f1311921d4f6d2913d503910f5c830a27d6bb7418d385aab8eb408f3
debug-demo_wait_group_cancel_failure
1.9 KB
sha256:1237e26b0a0e853692acf7c74a1087c349fde7542f16d2129e214ea52e2085e3
debug-demo_wait_group_loop_with_commands_failure
1.9 KB
sha256:91f151f64f98f934e940e8093270917900e8bd5a4536a2cdb4829000ca2bc414
debug-demo_wait_group_unexpected_commands_failure
1.9 KB
sha256:3f5711251c39e688272b3058ade97c88a83540075b17fedb7e7fd4581e2513a1
debug-demo_wait_group_with_commands
1.9 KB
sha256:b8dcbd1d2c7ce35f2bc050c952de9f8e643ba7bcb156e87d1d03391efc10f7ec
debug-infrastructure_suite
1.9 KB
sha256:3964edbae002273b499647e68cf6e9fa98e64f8489f88cbd0ab4b8e0d6339ccc
debug-options_suite_v1_option1
1.9 KB
sha256:118d074c488fc1d451bf95f074b39b7ddb9da018dad6b49a967ecf4dbf567ebb
debug-options_suite_v2_option3
1.9 KB
sha256:1237e26b0a0e853692acf7c74a1087c349fde7542f16d2129e214ea52e2085e3
debug-suite_a_against_suite_b_with_commands
1.9 KB
sha256:204dbaf9982251338646bc3dfe0eed69173c88adcd89cf82796e2e51457dcd64
debug-validator_suite_alternate_expected_file
1.9 KB
sha256:d8bf8ddc35a3d3b12f3f9b03d5192d0530dd89d2f43d053728dceb33ad92862a
debug-validator_suite_with_file_input
1.9 KB
sha256:b0cca199c23250e44c23e42215f38363980f7928f6267025d60b5708ea45e2a9