Closed deivid-rodriguez closed 4 years ago
The problem is that in some dev ruby builds, RUBY_PATCHLEVEL is -1, so the spec crashes because of an ill-formed requirement.
RUBY_PATCHLEVEL
-1
See for example https://github.com/rubygems/rubygems/pull/3077/checks?check_run_id=457988784.
My fix is to change the spec to respect a RUBY_PATCHLEVEL equal to -1, by reusing code that handles that case.
@bundlerbot merge
What was the end-user or developer problem that led to this PR?
The problem is that in some dev ruby builds,
RUBY_PATCHLEVEL
is-1
, so the spec crashes because of an ill-formed requirement.See for example https://github.com/rubygems/rubygems/pull/3077/checks?check_run_id=457988784.
What is your fix for the problem, implemented in this PR?
My fix is to change the spec to respect a
RUBY_PATCHLEVEL
equal to-1
, by reusing code that handles that case.