CODEWITHSUNDEEP
ruby-on-railsgoogle-chrometddcucumber
Aaron
Aaron

Reputation: 14029

Cucumber failing in chrome with "Retry later" message

I'm trying to run my cucumber tests and they seem to stop randomly. A new page is visited but nothing renders on the page except Retry later as in the following screenshot.

enter image description here

I'm on OS X 10.9.3, Chrome 35.0.1916.114, and running with bundle exec cucumber. It's happening in and Firefox also if I change the javascript driver.

Upvotes: 4

Views: 1384

Answers (1)

Aaron
Aaron

Reputation: 14029

The problem was not with Chrome, Cucumber, or Capybara. It was with Rack::Attack. 127.0.0.1 was whitelisted but according to this github issue

it wasn't whitelisting ipv6 and transitional loopback ip addresses

To simplify things I just moved Rack Attack to be production only.

tl;dr

Rack::Attack was to blame. Unless you need it in your test environment, just make the gem production only.

Upvotes: 15

Related Questions