-
Notifications
You must be signed in to change notification settings - Fork 561
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 Fault when running all specs with RSpec #208
Comments
You're 7 patch-level releases of Ruby 1.9.3 behind - could you please update to the latest 1.9.3-p392 and try again? |
I saw the same symptom on 1.9.3p374, but I no longer think it is coming from simplecov. It seems to happen when I change the Gemfile. Not only with simplecov. Have never seen this before...perhaps because I am working with threads. |
Alright, good luck figuring your problems out then! Maybe you can separate your specs into unit tests that test your individual components thread-less and a separate integration-style suite that puts it all together - I think that'd make it easier for you to find bugs in your threading implementation. I'd also strongly recommend checking out the celluloid gem when working with threads, it makes structuring and maintaining things a lot easier through things like supervision groups, though it surely is not applicable to everything. It's what the popular sidekiq gem uses under the hood, too. |
Getting same problem, also using rspec 2.12.0, Rails 3.2.x, OS X 10.7.5:
Fails when a require was pointing at something that was missing and immediately after reporting test results after running a set of tests. Fails every time. Simplecov works great for coverage in a gem I test with rspec, though, so I don't think is rspec. Trying to track down what is causing the problem. |
Now works great! Removed ruby-prof 0.11.2 (which was probably the problem) and switched to requiring/starting in initializer per this comment. |
guys, do you have any update about this? I have the same problem in jenkins |
I have the same issue on ruby 2.4.2 and simplecov 0.13, 0.14 and 0.15 |
Most likely it's a ruby bug. We don't usually segfault but the You can check that out by just doing:
http://ruby-doc.org/stdlib-2.3.0/libdoc/coverage/rdoc/Coverage.html Without a sample application there's probably also not much that ruby core can do. |
The following causes a segmentation fault, but only when simplecov is in Gemfile:
When set to false, there is no seg fault.
More RSpec config:
simplecov (0.7.1)
guard (1.6.2)
guard-rspec (2.4.1)
Ruby 1.9.3p125 and 1.9.3p374
The text was updated successfully, but these errors were encountered: