Selenium::WebDriver::Error::WebDriverError

[sebyx07]

I've also added this

  Capybara.register_driver :chrome do |app|
    capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
        chromeOptions: {
            args: %w[ no-sandbox headless disable-popup-blocking disable-gpu window-size=1920,1080]
        }
    )

    Capybara::Selenium::Driver.new(app, browser: :chrome, desired_capabilities: capabilities)
  end

error trace

   Selenium::WebDriver::Error::NoSuchDriverError:
            invalid session id
              (Driver info: chromedriver=2.42.591071 (0b695ff80972cc1a65a5cd643186d2ae582cd4ac),platform=Linux 4.15.0-36-generic x86_64)
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/response.rb:69:in `assert_ok'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/response.rb:32:in `initialize'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/common.rb:84:in `new'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/common.rb:84:in `create_response'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/default.rb:104:in `request'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/http/common.rb:62:in `call'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/bridge.rb:164:in `execute'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/oss/bridge.rb:584:in `execute'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/remote/oss/bridge.rb:152:in `window_handles'
          # /usr/local/bundle/gems/selenium-webdriver-3.14.1/lib/selenium/webdriver/common/driver.rb:185:in `window_handles'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara/selenium/driver.rb:193:in `window_handles'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara/selenium/driver_specializations/chrome_driver.rb:33:in `reset!'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara/session.rb:126:in `reset!'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara.rb:312:in `block in reset_sessions!'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara.rb:312:in `reverse_each'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara.rb:312:in `reset_sessions!'
          # /usr/local/bundle/gems/capybara-3.8.2/lib/capybara/rspec.rb:18:in `block (2 levels) in <main>'

Is there a way to run the tests parallel?

[grosser]

does https://github.com/grosser/parallel_tests/wiki#with-capybara040selenium----by-rgo help ?

[sebyx07]

have both of them added, same result

Capybara.default_driver = :chrome
Capybara.ignore_hidden_elements = false

port = 9887 + ENV['TEST_ENV_NUMBER'].to_i
Capybara.server_port = port
Capybara.session_name = port.to_s


if ENV['TEST_ENV_NUMBER']
  class Capybara::Server
    def find_available_port
      @port = 9887 + ENV['TEST_ENV_NUMBER'].to_i
    end
  end
end

Only the first driver, browser starts. the seconds throws the invalid session id

[grosser]

sorry, no idea .... if you find a solution please update the wiki page too :)

…

On Thu, Oct 11, 2018 at 12:54 AM sebyx07 ***@***.***> wrote: have both of them added, same result Capybara.default_driver = :chrome Capybara.ignore_hidden_elements = false port = 9887 + ENV['TEST_ENV_NUMBER'].to_i Capybara.server_port = port Capybara.session_name = port.to_s Only the first driver, browser starts. the seconds throws the invalid session id — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#658 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAsZ_EhJqbn-NkiRp2DTIeS9Dl1Xh1qks5ujvkmgaJpZM4XVE_T> .

[sebyx07]

Hey, got something that works. had to also configure the driver port.
here is the full config
Selenium::WebDriver::Error::NoSuchDriverError was raise because of insufficient resources, disabled with disable-dev-shm-usage

Capybara.default_driver = :chrome

port = 9887 + ENV["TEST_ENV_NUMBER"].to_i
Capybara.server_port = port

Capybara.register_driver :chrome do |app|
  capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
    chromeOptions: {
        args: %W(disable-dev-shm-usage disable-infobars disable-extensions no-sandbox headless disable-popup-blocking disable-gpu window-size=1280,1024)
    }
  )

  Capybara::Selenium::Driver.new(app,
                                 {
                                     browser: :chrome,
                                     desired_capabilities: capabilities,
                                     driver_opts: {
                                         port_server: 9515 + ENV["TEST_ENV_NUMBER"].to_i
                                     }
                                 }
  )
end

[maniax89]

@sebyx07 i am currently attempting to do something very similar with my setup (using https://github.com/flavorjones/chromedriver-helper)

require 'capybara/rails'
require 'capybara/rspec'
require 'capybara-screenshot/rspec'

Chromedriver::Helper.new.update
Capybara.server_host = "localhost"
test_run_int = (ENV["TEST_ENV_NUMBER"].try(:to_i) || 0)
port = 4000 + test_run_int
Capybara.server_port = port

Capybara.register_driver :headless_chrome do |app|
  browser_options = ::Selenium::WebDriver::Chrome::Options.new()
  browser_options.args << '--no-sandbox'
  browser_options.args << '--window-size=1280,1024'
  browser_options.args << '--disable-dev-shm-usage'
  browser_options.headless!

  Capybara::Selenium::Driver.new(app, browser: :chrome, options: browser_options, driver_opts: {
    port_server: 9515 + test_run_int
  })
end

Capybara::Screenshot.register_driver :headless_chrome do |driver, path|
  driver.browser.save_screenshot(path)
end

Capybara.javascript_driver = :headless_chrome

i just wanted to say that by adding disable-dev-shm-usage I was able to finally get this to work (after many hours of saying "it works locally on macosx, but not on a linux-based docker container")

leaving this here in case anyone else comes across this

[grosser]

awesome, thx! :)

[maniax89]

Yes, I think in my original issue it was all using docker containers (running on some flavor of Linux)

[lmansur]

I'm moving an application to a Docker environment, so one of the first steps is running CI in a docker container.

I was running into chrome not reachable error. After following https://github.com/grosser/parallel_tests/wiki#with-capybara040selenium----by-rgo, I started receiving another error (I think it was port related).

Adding disable-dev-shm-usage, as suggested by @maniax89, fixed the remaining errors. Now I can run my entire suite with parallel_test in a Docker container.

Thanks a lot fellas!