metasploit-framework
metasploit-framework copied to clipboard
Testing Ruby 3.2 against CI
Testing Ruby 3.2 against CI in order to get a grasp of what's failing.
Heads up looks like the Docker issue was related to the addition of Debug.gem though I'm curious why it decided to break now and not earlier; there are no dependency changes between this version and earlier versions so I'm curious if we forgot to bump the Docker related dependencies somehow?
The Ruby 3.2 failure is what I personally encountered when last testing this after the related Gems that were failing with 3.2 were updated, though not sure where there Sanity Test Execution is failing on, thats a new one for me 🤷
My bad, looking at this closer it looks like you stripped the linked dependencies from the Gemfile.lock for debug.gem somehow; might need to add those back in for Docker to pass?
Should look like this for reference:
debug (1.7.1)
irb (>= 1.5.0)
reline (>= 0.3.1)
@gwillcox-r7 Yea, I'm just getting around to the Docker stuff now and that was what the failing tests were telling me as well. So I'm reverting that now and will see how it goes 🤞
I believe they were removed when I ran bundle update
, can verify that if all goes green.
My bad, looking at this closer it looks like you stripped the linked dependencies from the Gemfile.lock for debug.gem somehow; might need to add those back in for Docker to pass?
Should look like this for reference:
debug (1.7.1) irb (>= 1.5.0) reline (>= 0.3.1)
After looking into this more, I can not replicate it. I was having some issues with having the wrong bundler version. I'm assuming that may be why this was changed. I can no longer replicate the issue after resolving my bundler issues 👍
My bad, looking at this closer it looks like you stripped the linked dependencies from the Gemfile.lock for debug.gem somehow; might need to add those back in for Docker to pass? Should look like this for reference:
debug (1.7.1) irb (>= 1.5.0) reline (>= 0.3.1)
After looking into this more, I can not replicate it. I was having some issues with having the wrong bundler version. I'm assuming that may be why this was changed. I can no longer replicate the issue after resolving my bundler issues 👍
I think Jeffery mentioned an issue with upgrading Bundler versions due to the fact that newer bundler versions don't allow having a single lock file for multiple OSes, so its possible you were running into some issues related to that? 🤷 Glad to hear its working now though 🥳
Release Notes
Adds support for Ruby 3.2