Open chrislloyd opened 11 years ago
Yep, seeing this too.
Pretty much a deal breaker.
I suspect https://github.com/sauce-labs/sauce_ruby/blob/master/lib/sauce/capybara.rb#L104 is causing it, will investigate.
Confirmed! Took that line out, all working. PR will come later.
This should be fixed in v2.4.6.
Ultimately, the root cause was a bug in Ruby, http://bugs.ruby-lang.org/issues/5218. This is fixed for Ruby 1.9.2-p392 but lower versions still have the issue.
This has broken again (between 1553347fdc24682e592a51796ed5b76f0223f08f and d9d5cb7a65851849f09d5407eae0f7ccab9941df ).
Hard to add tests for but it might be worth finding a way.
Hmm, I'll re-investigate.
I think there's a case for re-architecting all the current examples and tests into a set of standalone integration tests, then kicking them off in separate processes and checking for key outputs using IO objects and the like.
I'm having problems replicating this, even between those commits.
Does the current release version of the gem have the same problem? Can you attach a Gemfile.lock so I can try to replicate myself?
Gemfile*: https://gist.github.com/DanielHeath/5753478 Testing with latest master now.
Still (not) failing with latest master. Updated the gist with the new gemfile.
Some extra context: I'm running rake sauce:spec with a single browser configured. Doesn't matter which one I use (tried linux/win/osx with firefox/IE/chrome)
I think this has been fixed with 89abd334e38c4b55d15ecb348f6cfa970d2e1882, which has been released as 3.0.1. I was unable to repro for rspec
by itself still.
Here's what my test suite looks like without the Sauce gem required:
Then with the Sauce gem added (and no extra configuration):
This kind of breaks everything, but most importantly it breaks most CI.