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

Segmentation Faults in Ruby 2.4 #22

Open
plicjo opened this issue Mar 8, 2018 · 6 comments
Open

Segmentation Faults in Ruby 2.4 #22

plicjo opened this issue Mar 8, 2018 · 6 comments
Labels

Comments

@plicjo
Copy link

plicjo commented Mar 8, 2018

This gem fails on CI due to segmentation faults arising from the Ruby compiler.

You can see the problem in this 2.4 Travis build for the gem. https://travis-ci.org/CodementorIO/rest-firebase/jobs/296898566

@godfat
Copy link
Contributor

godfat commented Mar 8, 2018

Yeah, any idea how to solve this? This has been troubling me for a very long time, and I can't reproduce this locally at all. It seems it would only happen on Travis, on Ruby 2.4, and nothing else.

@plicjo
Copy link
Author

plicjo commented Mar 9, 2018

I've got it failing in the same way on Codeship (another CI tool), so it's not purely a Travis problem.

@godfat
Copy link
Contributor

godfat commented Mar 9, 2018

Was it also using pre-built binary from RVM?

$ rvm use 2.4 --install --binary --fuzzy

@godfat godfat added the bug label Mar 9, 2018
@plicjo
Copy link
Author

plicjo commented Mar 9, 2018

The commands that I'm using on Codeship are:

rvm use 2.4.3 --install
gem install bundler
bundle install
export RAILS_ENV=test
DISABLE_SPRING=true bundle exec rake parallel:load_schema
DISABLE_SPRING=true parallel_rspec spec

@plicjo
Copy link
Author

plicjo commented Mar 9, 2018

According to the Codeship docs, the Ruby versions are pre-installed. https://documentation.codeship.com/basic/languages-frameworks/ruby/#rvm

That might be a clue.

@godfat
Copy link
Contributor

godfat commented Mar 9, 2018

Thanks!

I really don't have any evidence at all, and I personally don't use rvm either. But I strongly suspect that RVM might have a broken pre-built Ruby 2.4, as it randomly happened for a long time, and I could never reproduce it locally.

Worst case, we'll never know, until we stop caring about 2.4.

Or if we could see it somewhere reproduced other than using RVM binary, that would be nice, and I could try to debug it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants