Errno::EPIPE: Broken pipe #68

xaviershay · 2011-05-29T04:53:27Z

I sporadically get the following error:

Errno::EPIPE: Broken pipe
  capybara-webkit-0.4.0/lib/capybara/driver/webkit/browser.rb:45:in `write'
  capybara-webkit-0.4.0/lib/capybara/driver/webkit/browser.rb:45:in `puts'
  capybara-webkit-0.4.0/lib/capybara/driver/webkit/browser.rb:45:in `command'
  capybara-webkit-0.4.0/lib/capybara/driver/webkit/browser.rb:18:in `find'
  capybara-webkit-0.4.0/lib/capybara/driver/webkit.rb:28:in `find'
  capybara-0.4.1.2/lib/capybara/node/finders.rb:156:in `find_in_base'
  capybara-0.4.1.2/lib/capybara/node/finders.rb:121:in `block in all'
  capybara-0.4.1.2/lib/capybara/node/finders.rb:120:in `map'
  capybara-0.4.1.2/lib/capybara/node/finders.rb:120:in `all'
  capybara-0.4.1.2/lib/capybara/node/matchers.rb:38:in `block in has_selector?'
  capybara-0.4.1.2/lib/capybara/node/finders.rb:164:in `block in wait_conditionally_until'
  capybara-0.4.1.2/lib/capybara/session.rb:222:in `block in wait_until'
  capybara-0.4.1.2/lib/capybara/util/timeout.rb:13:in `timeout'
  capybara-0.4.1.2/lib/capybara/session.rb:222:in `wait_until'
  capybara-0.4.1.2/lib/capybara/node/finders.rb:164:in `wait_conditionally_until'
  capybara-0.4.1.2/lib/capybara/node/matchers.rb:37:in `has_selector?'
  capybara-0.4.1.2/lib/capybara/node/matchers.rb:121:in `has_xpath?'
  capybara-0.4.1.2/lib/capybara/node/matchers.rb:184:in `has_content?'
  capybara-0.4.1.2/lib/capybara/session.rb:264:in `method_missing'

I am running my acceptance specs in parallel, if that is relevant.

The text was updated successfully, but these errors were encountered:

fwoeck · 2011-05-30T05:00:04Z

Hi, I see that too (ruby192, osx1067, guard, spork084) - primarily the very first time after I restarted the spork server. So it's a timing problem probably.
--Frank

fwoeck · 2011-05-31T09:27:45Z

Do you have
$.ajaxSetup({ async: true });
for your tests? See #71
--Frank

xaviershay · 2011-05-31T09:53:31Z

I don't have any JS - I'm testing the following rack application:

class MyApp
  def call(env)
    if env['PATH_INFO'] == '/home'
      [200, {'Content-Type' => 'text/plain'}, ["Hello world!"]]
    else
      [200, {'Content-Type' => 'text/plain'}, [""]]
    end
  end
end

lazylester · 2011-07-13T19:30:03Z

I'm seeing a similar problem. Repeatbly, in exactly the same place every time in my test suite. When I bypass webkit and use selenium for the failing test, the broken pipe error occurs on the next webkit test. And if I bypass webkit on that one, the error occurs on the next webkit test.

Broken pipe (Errno::EPIPE)
capybara-webkit-b6a09ee0bf3f/lib/capybara/driver/webkit/browser.rb:45:in `write'
capybara-webkit-b6a09ee0bf3f/lib/capybara/driver/webkit/browser.rb:45:in `puts'
capybara-webkit-b6a09ee0bf3f/lib/capybara/driver/webkit/browser.rb:45:in `command'
capybara-webkit-b6a09ee0bf3f/lib/capybara/driver/webkit/browser.rb:22:in `reset!'
capybara-webkit-b6a09ee0bf3f/lib/capybara/driver/webkit.rb:76:in `reset!'
capybara-1.0.0/lib/capybara/session.rb:70:in `reset!'
capybara-1.0.0/lib/capybara/dsl.rb:74:in `reset_sessions!'
capybara-1.0.0/lib/capybara/dsl.rb:74:in `each'
capybara-1.0.0/lib/capybara/dsl.rb:74:in `reset_sessions!'
capybara-1.0.0/lib/capybara/cucumber.rb:10:in `After'

bcardarella · 2011-07-23T07:03:28Z

Any updates on this?

sardaukar · 2011-08-23T13:34:31Z

Curious about the updates too...

leehambley · 2011-08-23T14:28:39Z

just a thought, but how does parallelizing your tests affect capybara webkit, if it forks after capybara webkit server starts, you'll have two clients sharing the same socket, that would result in this failure?

jasonm · 2011-09-17T21:14:51Z

I still see this, just tried switching out selenium for capybara-webkit master on a project (one I'm working on with @hgimenez):

  Scenario: A patient with no family history assigned                           # features/user/assign_family_history_to_patient.feature:17
    Then the "VITALS" tab should be active                                      # features/step_definitions/html_steps.rb:48
    When I follow "Social/Family" within the additional info tabs               # features/step_definitions/web_steps.rb:36
    Then the "SOCIAL/FAMILY" tab should be active                               # features/step_definitions/html_steps.rb:48
    And I should see "Assign Now" within the family history section             # features/step_definitions/web_steps.rb:36
    When I follow "Assign Now" within the family history section                # features/step_definitions/web_steps.rb:36
      No response received from the server. (Capybara::Driver::Webkit::WebkitNoResponseError)
      (eval):2:in `click_link'
      ./features/step_definitions/web_steps.rb:58:in `/^(?:|I )follow "([^"]*)"$/'
      features/user/assign_family_history_to_patient.feature:22:in `When I follow "Assign Now" within the family history section'
    Then the "Family History" field should be focused                           # features/step_definitions/form_steps.rb:71
    When I fill in "Family History" with "History of baconizers"                # features/step_definitions/web_steps.rb:61
    And I press "Save"                                                          # features/step_definitions/web_steps.rb:53
    Then I should see "History of baconizers" within the family history section # features/step_definitions/web_steps.rb:36
    And I should not see "Assign Now" within the family history section         # features/step_definitions/web_steps.rb:36
    And I see the edit family history link                                      # features/step_definitions/selector_steps.rb:5
      Broken pipe (Errno::EPIPE)
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/bundler/gems/capybara-webkit-f493b22f6bb5/lib/capybara/driver/webkit/browser.rb:66:in `write'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/bundler/gems/capybara-webkit-f493b22f6bb5/lib/capybara/driver/webkit/browser.rb:66:in `puts'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/bundler/gems/capybara-webkit-f493b22f6bb5/lib/capybara/driver/webkit/browser.rb:66:in `command'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/bundler/gems/capybara-webkit-f493b22f6bb5/lib/capybara/driver/webkit/browser.rb:32:in `reset!'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/bundler/gems/capybara-webkit-f493b22f6bb5/lib/capybara/driver/webkit.rb:85:in `reset!'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/gems/capybara-1.0.1/lib/capybara/session.rb:70:in `reset!'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/gems/capybara-1.0.1/lib/capybara/dsl.rb:74:in `block in reset_sessions!'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/gems/capybara-1.0.1/lib/capybara/dsl.rb:74:in `each'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/gems/capybara-1.0.1/lib/capybara/dsl.rb:74:in `reset_sessions!'
      /Users/jason/.rvm/gems/ruby-1.9.2-p290/gems/capybara-1.0.1/lib/capybara/cucumber.rb:10:in `After'

@halogenandtoast @jferris do you guys ever see this on an app?

jferris · 2011-09-19T13:49:37Z

A broken pipe happens when the webkit_server binary crashes, so it always indicates a bug in capybara-webkit. Unfortunately, it's frequently difficult to find out what actually caused it to crash. What actually happens when you follow "Assign Now" in the above scenario?

jasonm · 2011-09-19T14:29:05Z

"Assign Now" is a placeholder link for a set of unassigned attributes on a Patient model. When you click it, the placeholder markup is replaced with an editable form in a Backbone.js view. The link is "#edit-family-history" and click is bound to renderForm in this view: https://gist.github.com/dddd26ba632cdac725ba

tmaier · 2011-09-28T10:08:33Z

I have the same problem.

If i run my js: true related specs individually, they pass.
But when I run more then one spec with js: true, the second fails with Errno::EPIPE: Broken pipe

I tried now for one hour to nail it down to a as simple as possible example.
But unfortunately I could not find one.
Even simple examples with just one visit and fill_in tend to fail, but not always.

If there is any way how I can assist you to find the error, I'm happy to help.

carlhoerberg · 2011-09-28T10:09:00Z

when using :webkit_debug we don't get these broken pipe errors.. (newly installed ubuntu 11.04 machine, mac os lion no such errors even with the normal :webkit driver)

tmaier · 2011-09-28T10:20:00Z

Thank you @carlhoerberg for this hint.

I tried it. The first one still passes, starting from the second one it fails.

[first one omitted]
People
  POST /people/12345/destroy
 >> Visit
 >> 1
 >> 36
 >> http://127.0.0.1:65185/users/sign_in
 << 
 >> Reset
 >> 0
    destroy person (FAILED - 1)

Projects
 >> Visit
 >> Reset
  works (FAILED - 2)
 >> Visit
 >> Reset
  works also (FAILED - 3)

WorkBreakdownStructures
  GET /projects/12345/work_breakdown_structures/12345/destroy
 >> Visit
 >> Reset
    destroy work breakdown structure (FAILED - 4)

Failures:

  1) People POST /people/12345/destroy destroy person
     Failure/Error: login_as user
     Capybara::Driver::Webkit::WebkitNoResponseError:
       No response received from the server.
     # ./spec/support/auth_methods.rb:14:in `login_as'
     # ./spec/requests/people_spec.rb:12:in `block (2 levels) in <top (required)>'

  2) Projects works
     Failure/Error: visit root_path
     Errno::EPIPE:
       Broken pipe
     # ./spec/requests/projects_spec.rb:199:in `block (2 levels) in <top (required)>'

  3) Projects works also
     Failure/Error: visit root_path
     Errno::EPIPE:
       Broken pipe
     # ./spec/requests/projects_spec.rb:210:in `block (2 levels) in <top (required)>'

  4) WorkBreakdownStructures GET /projects/12345/work_breakdown_structures/12345/destroy destroy work breakdown structure
     Failure/Error: login_as user
     Errno::EPIPE:
       Broken pipe
     # ./spec/support/auth_methods.rb:14:in `login_as'
     # ./spec/requests/work_breakdown_structures_spec.rb:8:in `block (2 levels) in <top (required)>'```

joshuaclayton · 2011-09-30T15:58:34Z

Also seeing these issues, but there's no rhyme or reason. The test suite's been running for a couple hours fine but then different steps start failing. Running the scenarios individually don't result in the exception.

Running against thoughtbot/capybara-webkit HEAD.

[ ~/dev/project webkitupgrade ✔ ] ps aux | grep webkit_server
joshuaclayton  44486   0.2  0.5  4686236  46064 s002  S     3:29PM   0:21.21 /Users/joshuaclayton/.rvm/gems/ruby-1.9.2-p180/bundler/gems/capybara-webkit-eeeddbd07241/bin/webkit_server
joshuaclayton  50944   0.0  0.6  4686180  50936 s002  S    11:53AM   0:54.49 /Users/joshuaclayton/.rvm/gems/ruby-1.9.2-p180/bundler/gems/capybara-webkit-cc2e9486a0ce/bin/webkit_server
joshuaclayton  82645   0.0  0.0        0      0 s002  Z    10:08AM   0:00.00 (webkit_server)
joshuaclayton  28948   0.0  0.0  2426700    340 s013  S+   11:53AM   0:00.00 grep webkit_server

jferris · 2011-10-01T17:36:52Z

I think this could be a duplicate of #39. Can you guys try again on 0.7.1? If you keep running into issues, please open a new issue and include output from :webkit_debug.

tmaier · 2011-10-04T07:41:26Z

Thank you @jferris, but the update did not solve my issue.
I created a followup issue #181.

FlaviuSim · 2011-11-08T21:11:53Z

I was having this issue on 0.6.1 (especially with devise paths (e.g.: visit login_path)).

After upgrading to 0.7.2, the problem was solved. Just an fyi for the people coming to this page like I did.

Thank you for making testing easier.

enricribas · 2011-12-05T14:53:56Z

We are still having the same issue with capybara-webkit 0.7.2
Running integration test passes when run individually but fails when an integration test with js=> true runs (and passes) before it.
The test that fails does not have js=>true needed. This second tests fails with 'broken pipe'.

Any ideas greatly appreciated. Thanks.

iRonin · 2012-09-19T08:51:55Z

I'm getting Errno::EPIPE: Broken pipe on e39a5c9 but it's working fine on e677cb9

mhoran · 2012-09-19T11:38:34Z

@iRonin, this is likely related to the segfaults being discussed in #376. The logging introduced in d9b1898 makes the errors more prevalent. If you run with Qt 4.7.4 the segfaults will likely go away.

iRonin · 2012-09-19T18:14:12Z

@mhoran Thanks, I'll try to give it a go :)

kylewelsby · 2012-12-18T15:37:38Z

Im running QT 4.8.4 and I get

Capybara::Driver::Webkit::WebkitNoResponseError:
       No response received from the server.

then on the next example

Errno::EPIPE:
       Broken pipe

haarts · 2012-12-18T20:35:31Z

+1
Got the same error as @kylefiedler

mhoran · 2012-12-19T04:09:21Z

@kylewelsby, @haarts, please try out the latest master, bca84f9. If you continue to experience segfaults, please follow the instructions in #380.

haarts · 2012-12-19T08:15:50Z

Rock on. Commenting out font-awesome worked for me. I used http://spin.atomicobject.com/2012/09/05/font-awesome-capybara-webkit/

kylewelsby · 2012-12-19T09:59:37Z

My setup now

Gemfile
gem 'capybara' #v2.0.1
gem 'capybara-webkit', :git => 'git://github.com/thoughtbot/capybara-webkit.git' # bca84f9

A few tests pass then,

     Capybara::Driver::Webkit::WebkitNoResponseError:
       No response received from the server.

followed by

     Errno::EPIPE:
       Broken pipe

mhoran · 2012-12-19T12:37:10Z

@kylewelsby, could you open a new issue? It looks like you're experiencing something different than the others, and I don't want to clutter this thread. Please confirm that you are not using font-awesome. Then, please provide output from the failing scenario with the :webkit_debug driver and follow the instructions in #380 for retrieving a backtrace.

synth · 2013-04-15T20:42:02Z

i might add a possible solution that seems to work for me for the moment. I discovered that there are times after running some specs that fail or crash that there might be lingering(orphaned?) webkit/rspec processes. I continue to get broken pipe while these processes exist even though they're not in the foreground anymore of where I ran them. I use the following command to clear everything out:

ps -ef |egrep 'webkit|rspec' |awk '{print $2}' |xargs kill -9

there's probably a more slick unix command, so feel free to update with a better way...

nmccready · 2013-09-06T20:30:23Z

please disregard issue as it is relevant to puma as well

Dan2552 · 2013-11-26T10:18:30Z

I'm getting this issue on my OS X Mavericks setup. Could this be because homebrew suggested to install QT using --HEAD?

jeremylynch · 2014-09-08T12:08:44Z

I had a similar issue as described above that I was able to solve by upgrading Qt

jferris closed this as completed Oct 1, 2011

tmaier mentioned this issue Feb 22, 2012

I still get WebkitNoResponseError #181

Closed

nmccready mentioned this issue Sep 6, 2013

requests failing sometimes puma/puma#274

Closed

rosskevin mentioned this issue Feb 12, 2015

Errno::ECONNRESET: Connection reset by peer on Ubuntu 13.04 #540

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Errno::EPIPE: Broken pipe #68

Errno::EPIPE: Broken pipe #68

xaviershay commented May 29, 2011

fwoeck commented May 30, 2011

fwoeck commented May 31, 2011

xaviershay commented May 31, 2011

lazylester commented Jul 13, 2011

bcardarella commented Jul 23, 2011

sardaukar commented Aug 23, 2011

leehambley commented Aug 23, 2011

jasonm commented Sep 17, 2011

jferris commented Sep 19, 2011

jasonm commented Sep 19, 2011

tmaier commented Sep 28, 2011

carlhoerberg commented Sep 28, 2011

tmaier commented Sep 28, 2011

joshuaclayton commented Sep 30, 2011

jferris commented Oct 1, 2011

tmaier commented Oct 4, 2011

FlaviuSim commented Nov 8, 2011

enricribas commented Dec 5, 2011

iRonin commented Sep 19, 2012

mhoran commented Sep 19, 2012

iRonin commented Sep 19, 2012

kylewelsby commented Dec 18, 2012

haarts commented Dec 18, 2012

mhoran commented Dec 19, 2012

haarts commented Dec 19, 2012

kylewelsby commented Dec 19, 2012

mhoran commented Dec 19, 2012

synth commented Apr 15, 2013

nmccready commented Sep 6, 2013

Dan2552 commented Nov 26, 2013

jeremylynch commented Sep 8, 2014

Errno::EPIPE: Broken pipe #68

Errno::EPIPE: Broken pipe #68

Comments

xaviershay commented May 29, 2011

fwoeck commented May 30, 2011

fwoeck commented May 31, 2011

xaviershay commented May 31, 2011

lazylester commented Jul 13, 2011

bcardarella commented Jul 23, 2011

sardaukar commented Aug 23, 2011

leehambley commented Aug 23, 2011

jasonm commented Sep 17, 2011

jferris commented Sep 19, 2011

jasonm commented Sep 19, 2011

tmaier commented Sep 28, 2011

carlhoerberg commented Sep 28, 2011

tmaier commented Sep 28, 2011

joshuaclayton commented Sep 30, 2011

jferris commented Oct 1, 2011

tmaier commented Oct 4, 2011

FlaviuSim commented Nov 8, 2011

enricribas commented Dec 5, 2011

iRonin commented Sep 19, 2012

mhoran commented Sep 19, 2012

iRonin commented Sep 19, 2012

kylewelsby commented Dec 18, 2012

haarts commented Dec 18, 2012

mhoran commented Dec 19, 2012

haarts commented Dec 19, 2012

kylewelsby commented Dec 19, 2012

mhoran commented Dec 19, 2012

synth commented Apr 15, 2013

nmccready commented Sep 6, 2013

Dan2552 commented Nov 26, 2013

jeremylynch commented Sep 8, 2014