fix(ci): fix Ruby integration test failures#158
Merged
Conversation
- Use 'all' source selection in rbenv migration tests (macOS and Ubuntu) to handle cases where system Ruby is detected before rbenv - Handle GitHub API rate limiting (HTTP 403/429) gracefully in Ruby integration test version verification step
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
The integration tests were failing due to:
"1\n0\nn\n"was selecting the system Ruby (3.3.10) instead of the rbenv-installed version (3.3.6).list-all rubyto fail, which blocked the entire test run.Solution
"all\n0\nn\n"to select all sources, similar to the uru migration fix in fix(ci): enable all migrations and fix uru version selection #157Test plan
npm run checkpasses (format, lint, tests)