Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix test failure when version is exactly 3.2 #4106

Merged
merged 1 commit into from Dec 7, 2020
Merged

Fix test failure when version is exactly 3.2 #4106

merged 1 commit into from Dec 7, 2020

Commits on Dec 7, 2020

  1. Fix test failure when version is exactly 3.2 

    In the stable branch (when version is exactly 3.2), this test fails
because rubygems updater aborts early in the specific case when we are
upgrading to the exact same rubygems version being run with an "already
installed" message.

To fix this problem, I change the test to use the earliest possible 3.2
prerelease, which is the same version that shipped the new layout and
it's a past release so it should pass consistently no matter when the
running rubygems release is.
    @deivid-rodriguez
    deivid-rodriguez committed Dec 7, 2020
    Copy the full SHA
    ef70538 View commit details
    Browse the repository at this point in the history