Temporarily exclude Ruby 3.2 build with Rails 8.1 #956
Conversation
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
y-yagi
changed the title
Collaborator
Author
|
I ran CI 5 times with this branch and all builds were succeeded. |
Alexander-Senko
approved these changes
Nov 16, 2025
y-yagi
force-pushed
the
exclude_ruby32_with_rails81
branch
from
e2c7913 to
472e7d9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
I am investigating unstable tests in #955.
It seems that it often happens in the DB setup for
productionenvironment with Ruby 3.2 + Rails 8.1 build.I'm sure why yet, unstable build prevents other PRs. So I would like to disable it temporarily.
I think disabling isn't a big issue because Ruby 3.2 and Rails 8.1 tests are running with other combinations.