Skip to content
This repository has been archived by the owner on Nov 27, 2020. It is now read-only.

Tests with phantomjs - sometimes green sometimes red. #340

Closed
panSarin opened this issue Jun 12, 2013 · 15 comments
Closed

Tests with phantomjs - sometimes green sometimes red. #340

panSarin opened this issue Jun 12, 2013 · 15 comments

Comments

@panSarin
Copy link

About 50% times when i run my test it return ok, but in other 50% times it is failure.
Sometimes with:

     Failure/Error: click_button 'Lorem'
     Capybara::Poltergeist::DeadClient:
       PhantomJS client died while processing {"name":"click","args":[3,3]}

and sometimes even earlier with:

     Failure/Error: visit some_path(@some.id)
     Capybara::Poltergeist::DeadClient:
       PhantomJS client died while processing {"name":"visit","args":["http://localhost:54544/some_path/4"]}

Any ideas?

@szymon-przybyl
Copy link

Maybe this will help you: ariya/phantomjs#11252

@yaauie
Copy link
Contributor

yaauie commented Jul 22, 2013

@panSarin Can you upgrade your phantomjs to ~> 1.9.1 and report back on whether or not that fixed the flapping?

@Karueglazki
Copy link

Hello.
sorry, i have the same problem.
phantomjs 1.9.1

@oelmekki
Copy link

I often have this kind of error on my CI server too (not 50% of time,
though, more something like 10%).

Obviously, this is just a symptom (potentially even different
problems). I can't remember seeing it happen locally (but then again,
I don't run the whole integration suite much locally). Could it be
related to whatever allows poltergeist to run without a X server
running ?

Anyway, as it happens on CI, I can't provide a --seed option to rspec
to run in the same order again and see if it is reproducible. I usually
just try again and it passes. If anyone has an idea of what I could do
to have useful info, it would be great.

@rileytg
Copy link

rileytg commented Oct 23, 2014

I'm also getting a roughly 10% failure on Travis CI

@salimane
Copy link

salimane commented Nov 7, 2014

+1

@morgandonze
Copy link

I'm experiencing this problem too.

@karolxavierleite
Copy link

+1

I'm having the same problem. I'm using poltergeist with Capybara.

My versions:
poltergeist: 1.5.0
phantomJS: 1.9.7
capybara: 2.2.1

@cassioscabral
Copy link

+1

I'm having the same problem. I'm using poltergeist with Capybara.

My versions:
poltergeist: 1.4.1
phantomJS: 1.9.8
capybara: 2.1.0

@pahlawat
Copy link

+1
Having same issue, tests run locally but not running on CI

@khaidpham
Copy link

+1
Was having the same issue with poltergeist 1.5.1 and phantomJS 1.9.8, phantomJS crashed when visit() certain sites with some js errors
However, after uninstalling phantomJS 1.9.8 and install the latest phantomJS 2.0, visiting the same sites no longer crash phamtomJS

@hamza88
Copy link

hamza88 commented Jul 28, 2015

Tried downgrading to Phantomjs to 1.9.8 whilst using capybara 2.2.1 and Poltergeist 1.5.1 ... no luck. Have experimented with versions.

Still getting inconsistent results ...

@pixelpax
Copy link

I upgraded to PhantomJS 2.0 (compiled from source on Ubuntu) and it finally works! Tried six other version combinations with no luck. I am sometimes getting a 'Timeout Error'. Will continue experimenting with other versions of Capybara and Poltergeist.

Capybara 2.4.4
Poltergeist 1.6.0
PhantomJS 2.0.0

@Dfenniak
Copy link

I have the exact versions mentioned above and I'm still seeing the issue.

@twalpole
Copy link
Contributor

I'm closing this due to the age of the original issue and the fact no one has actually posted any real details about the issues or a reproducible test case - If anyone is having actual issues, please open a new issue with real details about all versions used, details of the tests that are failing, and if possible a reproducible minimal test case

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

No branches or pull requests