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.

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

Skip nested IRB tests in Ruby Core CI #675

Merged
merged 1 commit into from
Aug 9, 2023
Merged

Skip nested IRB tests in Ruby Core CI #675

merged 1 commit into from
Aug 9, 2023

Conversation

st0012
Copy link
Member

@st0012 st0012 commented Aug 9, 2023

Sometimes (or under some environments) the subprocess gets stuck in the nested IRB session until timed out (example). We don't have enough information to debug it yet, so skip the tests to unblock CI.

Sometimes the subprocess gets stuck in the nested IRB session until timed
out. We don't have enough information to debug it yet, so skip the tests
to unblock CI.
@st0012 st0012 merged commit 606f18c into master Aug 9, 2023
47 checks passed
@st0012 st0012 deleted the fix-ruby-ci branch August 9, 2023 22:28
matzbot pushed a commit to ruby/ruby that referenced this pull request Aug 9, 2023
(ruby/irb#675)

Sometimes the subprocess gets stuck in the nested IRB session until timed
out. We don't have enough information to debug it yet, so skip the tests
to unblock CI.

ruby/irb@606f18c80c
st0012 added a commit that referenced this pull request Aug 11, 2023
We already skipped history integration tests in core CI in #675 due to
suspicion on nested IRB sessions don't work on certain operating systems.

But after #669, the evaluation integration test also started to fail on
some Core CI suites. So, it looks like the integration test setup may not
work in Core CI, at least in some suites.

Consider `ruby/irb` already has rather sophisticated test suite, I think
it's better to skip the integration tests in core CI for now.
st0012 added a commit that referenced this pull request Aug 11, 2023
We already skipped history integration tests in core CI in #675 due to
suspicion on nested IRB sessions don't work on certain operating systems.

But after #669, the evaluation integration test also started to fail on
some Core CI suites. So, it looks like the integration test setup may not
work in Core CI, at least in some suites.

Consider `ruby/irb` already has rather sophisticated test suite, I think
it's better to skip the integration tests in core CI for now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant