Rspec : PG::ConnectionBad: PQsocket() can't get socket descriptor

ruby-on-rails rspec rspec-rails
ishwr picture ishwr · May 13, 2014 · Viewed 8.3k times · Source

I run my rspec and most of the test were failed. I got the same error for them, which is:

    Failure/Error: Unable to find matching line from backtrace
    ActiveRecord::StatementInvalid:
    PG::ConnectionBad: PQsocket() can't get socket descriptor: BEGIN

I found a question that is similar to my problem, but there is no answer yet and I also tried the solution from this link, but it didn't make any differences for me. I opened my test console and run some simplest queries and it worked.

Answer

Brandon McKay picture Brandon McKay · Mar 26, 2015

There may be a problem with pg: '0.18.1'. I tried reverting to 0.18.0, and I believe the problem has gone away.

I'll open up an issue on the repo after testing a bit more locally. I added this issue on the pg repo.

EDIT: I was wrong. What did in fact help though, was installing the spring-commands-rspec gem. I think what it ended up doing for me was caching it in a state where it worked. Although it could also just as easily cache it in a state where it didn't.

Related questions

Rails 3.1, RSpec: testing model validations

I have started my journey with TDD in Rails and have run into a small issue regarding tests for model validations that I can't seem to find a solution to. Let's say I have a User model, class User < …

Read More
How do I get an ENV variable set for rspec?

I'm using foreman to start up my rails development server. It's nice that I can put all of my environment variables in the .env file. Is there a way to do something similar for my test environment? I want to …

Read More
Factory-girl create that bypasses my model validation

I am using Factory Girl to create two instances in my model/unit test for a Group. I am testing the model to check that a call to .current returns only the 'current' groups according to the expiry attribute as …

Read More