Skip to content

Mitigate truffleruby failure by using unreleased stringio gem - #790

Closed
st0012 wants to merge 1 commit into
masterfrom
mitigate-truffleruby-failure
Closed

Mitigate truffleruby failure by using unreleased stringio gem#790
st0012 wants to merge 1 commit into
masterfrom
mitigate-truffleruby-failure

Conversation

@st0012

Copy link
Copy Markdown
Member

The fix has been merged but not released yet: ruby/stringio#71

@eregon

Copy link
Copy Markdown
Member

Shouldn't be necessary anymore (stringio 3.1.0 was released)

@st0012
st0012force-pushed the mitigate-truffleruby-failure branch from f495997 to 46df4f2CompareNovember 28, 2023 10:48
@eregon

Copy link
Copy Markdown
Member

But unfortunately there seems to be some not updated cache or so yet in rubygems.org :/
ruby/stringio#71 (comment)

@eregon

Copy link
Copy Markdown
Member

The failure on https://github.com/ruby/irb/actions/runs/7017641177/job/19091354167?pr=790#step:3:87 is due to the debug gem using RBASIC()->flags too.
I'll make a PR.

@eregon

Copy link
Copy Markdown
Member

ruby/debug#1039

@garyhtougaryhtou mentioned this pull request Nov 30, 2023
@st0012st0012 closed this Dec 1, 2023
@st0012

Copy link
Copy Markdown
MemberAuthor

@eregon Thanks for the context and the PR on debug 🙏
Since the goal is to test compilation against TruffleRuby directly in debug repo, I added #796 to skip installing debug with TruffleRuby in IRB.

@st0012
st0012 deleted the mitigate-truffleruby-failure branch December 1, 2023 22:07
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@st0012@eregon