Segmentation fault while running tests for latest Rails 4.2

Meghali

unread,

Aug 4, 2015, 11:09:29 AM8/4/15

to Ruby on Rails: Core

Hi All,

I am trying to build Rails from source for the latest stable (4.2) version from the branch 4-2-stable; however I am facing issue while running the tests.

I am getting a segmentation fault at 'activesupport' for rake tests.

Has anyone already seen this error before? Can someone help me fix this test-case?

The details of error log are as below:

Platform I am trying on: Ubuntu 14.10

Rails Version: 4.2.3

Ruby Version: 2.2.2 & 2.1.6 (on both versions getting same trace)

Command used:

$ bundle exec rake test --trace

====================

** Invoke test (first_time)

** Execute test

/home/test/.rvm/rubies/ruby-2.1.6/bin/ruby -w -I"lib:test" -I"/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib" "/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/rake_test_loader.rb" "test/**/*_test.rb"

Run options: --seed 36135

# Running:

..................................................................................................................................................................................................................................................................

...............................................................................................................................................................................................................................................................

................................................................................................................................................................................ Segmentation fault

rake aborted!

Command failed with status (139): [ruby -w -I"lib:test" -I"/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib" "/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/rake_test_loader.rb" "test/**/*_test.rb" ]

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/testtask.rb:108:in `block (3 levels) in define'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/file_utils.rb:57:in `call'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/file_utils.rb:57:in `sh'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/file_utils_ext.rb:37:in `sh'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/file_utils.rb:96:in `ruby'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/file_utils_ext.rb:37:in `ruby'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/testtask.rb:104:in `block (2 levels) in define'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/file_utils_ext.rb:58:in `verbose'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/testtask.rb:100:in `block in define'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'

/home/test/.rvm/rubies/ruby-2.1.6/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'

/home/test/.rvm/gems/ruby-2.1.6/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'

/home/test/.rvm/gems/ruby-2.1.6/bin/rake:23:in `load'

/home/test/.rvm/gems/ruby-2.1.6/bin/rake:23:in `<main>'

/home/test/.rvm/gems/ruby-2.1.6/bin/ruby_executable_hooks:15:in `eval'

/home/test/.rvm/gems/ruby-2.1.6/bin/ruby_executable_hooks:15:in `<main>'

Tasks: TOP => test

test@pts00433-vm26:~/meghali/rails-4.2.3/rails/activesupport$

test@pts00433-vm26:~/meghali/rails-4.2.3/rails/active

===================

Thanks in advance.

Meghali

unread,

Aug 24, 2015, 1:58:10 AM8/24/15

to Ruby on Rails: Core

In addition to the details above, I would like to mention here that I am getting this specific issue on Power system (ppc64le).

Let me know if anyone has seen similar problem.

Thanks!

Rishav Rastogi

unread,

Aug 24, 2015, 2:08:34 AM8/24/15

to rubyonra...@googlegroups.com

Hi Meghali,

Please use the ruby-on-rails-talk google group or stackoverflow to post this question. This group is for the discussions related to the development of the Rails framework, not with.

Thanks

Rishav

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-co...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

--

Rishav Rastogi
http://twitter.com/rishavrastogi
Cell : +91 9676086910
Gtalk : rishav.rastogi
Skype : rishavrastogi

Ryan Bigg

unread,

Aug 24, 2015, 2:09:38 AM8/24/15

to rubyonra...@googlegroups.com, rubyonra...@googlegroups.com

I think that Meghali was in the right here. This is most definitely a core framework development question.

Meghali

unread,

Aug 24, 2015, 2:45:47 AM8/24/15

to Ruby on Rails: Core

Thanks Rishav and Ryan for responding.

I am following up for this on ruby-on-rails-talk community as well as on stack-overflow already.

-Meghali

te...@pts00433-vm26:~/meghali/rails-4.2.3/rails/activesupport$

te...@pts00433-vm26:~/meghali/rails-4.2.3/rails/activesupport$
te...@pts00433-vm26:~/meghali/rails-4.2.3/rails/active
===================

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-co...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

--
Rishav Rastogi
http://twitter.com/rishavrastogi
Cell : +91 9676086910
Gtalk : rishav.rastogi
Skype : rishavrastogi

Priya Duggirala

unread,

Aug 25, 2015, 11:23:12 AM8/25/15

to Ruby on Rails: Core

Hi Meghali ,

I was facing similar segmentation faults while running tests in the activesupport dir.

Reply all

Reply to author

Forward