Skip to content
Command Shell Acceptance

Bump version of framework to 6.4.138 #4922

Sign in to view logs

Bump version of framework to 6.4.138

Bump version of framework to 6.4.138 #4922

Triggered via push June 11, 2026 10:11
@jenkins-eks-metasploitjenkins-eks-metasploit[bot]
pushed 0332a35
master
Status Success
Total duration 9m 48s
Artifacts 9

command_shell_acceptance.yml

on: push
Matrix: test
Generate report
39s
Generate report
Fit to window
Zoom out
Zoom in

Annotations

16 warnings and 1 notice
linux ubuntu-latest
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, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
linux ubuntu-latest
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
python_ssl_2_7 ubuntu-latest
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, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
python_ssl_2_7 ubuntu-latest
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
python_ssl_3_4 ubuntu-latest
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, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
python_ssl_3_4 ubuntu-latest
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
python_ssl_2_6 ubuntu-latest
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, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
python_ssl_3_13 ubuntu-latest
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, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
cmd 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/upload-artifact@v4, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
cmd windows-2022
Cache not found for keys: setup-ruby-bundler-cache-v6-windows-2022-x64-ruby-3.4.3-wd-D:\a\metasploit-framework\metasploit-framework\metasploit-framework-with--without-coverage development-only--v-5-Gemfile.lock-f747ea54af063a5ad75865d2e6fda7e1c2713607d149b16f4624692f6369b076, setup-ruby-bundler-cache-v6-windows-2022-x64-ruby-3.4.3-wd-D:\a\metasploit-framework\metasploit-framework\metasploit-framework-with--without-coverage development-only--v-5-Gemfile.lock-
powershell windows-2025
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, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
powershell windows-2025
Cache not found for keys: setup-ruby-bundler-cache-v6-windows-2025-x64-ruby-3.4.3-wd-D:\a\metasploit-framework\metasploit-framework\metasploit-framework-with--without-coverage development-only--v-5-Gemfile.lock-f747ea54af063a5ad75865d2e6fda7e1c2713607d149b16f4624692f6369b076, setup-ruby-bundler-cache-v6-windows-2025-x64-ruby-3.4.3-wd-D:\a\metasploit-framework\metasploit-framework\metasploit-framework-with--without-coverage development-only--v-5-Gemfile.lock-
powershell 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/upload-artifact@v4, ruby/setup-ruby@eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
powershell windows-2022
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
powershell windows-2022
Cache not found for keys: setup-ruby-bundler-cache-v6-windows-2022-x64-ruby-3.4.3-wd-D:\a\metasploit-framework\metasploit-framework\metasploit-framework-with--without-coverage development-only--v-5-Gemfile.lock-f747ea54af063a5ad75865d2e6fda7e1c2713607d149b16f4624692f6369b076, setup-ruby-bundler-cache-v6-windows-2022-x64-ruby-3.4.3-wd-D:\a\metasploit-framework\metasploit-framework\metasploit-framework-with--without-coverage development-only--v-5-Gemfile.lock-
Generate report
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
powershell windows-2025
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
final-report-27339663652
1.03 MB
sha256:d2a267a1c633f445c33d0845349ffe4dee4033143a130c883e3ec8b23cf81ab7
raw-data-cmd--windows-2022
17.1 KB
sha256:1191891a5c4852d348daeee62f7c0b007d8ca222619574a1da24d6d3011d2520
raw-data-linux--ubuntu-latest
16.9 KB
sha256:bd8edf527e5630b16f29d2dc89cfc8a0d82c9f5d7631b596a5d52f18b65f832b
raw-data-powershell--windows-2022
17.4 KB
sha256:b93c0123df77978fe54b4c301ca1b881d7fb2730de37a228f33883b7c6e58c11
raw-data-powershell--windows-2025
17.4 KB
sha256:a1f548f8ea0e87402f90351402ce3f91cc11e7ab85d905c5a99af0620aad7579
raw-data-python_ssl_2_6--ubuntu-latest
10.7 KB
sha256:ce30f6e5003cfa2408339e5f4220cc01d3837dd0f6578702d16dfd53ec05afab
raw-data-python_ssl_2_7--ubuntu-latest
10.7 KB
sha256:d7f1a578987390ed927bc98c33aa2d152681c2c23df123575390045fffe80884
raw-data-python_ssl_3_13--ubuntu-latest
10.7 KB
sha256:9248a6c80172be0e3e2a48868698e920fa00a39863d4e299a70876a074240a27
raw-data-python_ssl_3_4--ubuntu-latest
10.7 KB
sha256:621ba89fb0cd598459a68d13d10d57ee9bcdeed53ff7b01966a1def5a3988900