Selenium WebDriver does not work

lzap · June 14, 2021, 1:21pm

Hey,

I cannot get webdriver working. No matter what I do, when I try to start it, I am getting:

require "selenium-webdriver"
driver = Selenium::WebDriver.for :chrome

Selenium::WebDriver::Error::UnknownError (unknown error: Chrome failed to start: exited abnormally.)
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/lib64/chromium-browser/chromium-browser is no longer running, so ChromeDriver is assuming that Chrome has crashed.)

Then I need to kill the process. Any clue how to troubleshoot this? All JS webdriver tests do fail and are extremely slow.

lzap · June 14, 2021, 1:38pm

Weird I googled this out and adding headless parameter works, I just do not know how to add this to Foreman configuration:

require "selenium-webdriver"
options = Selenium::WebDriver::Chrome::Options.new
options.add_argument('--headless')
options.add_argument('--no-sandbox')
options.add_argument('--disable-dev-shm-usage')
options.add_argument('--ignore-certificate-errors')
driver = Selenium::WebDriver.for :chrome, options: options

lzap · June 14, 2021, 1:45pm

Weird we do set those arguments in the codebase:

github.com

theforeman/foreman/blob/develop/test/integration_test_helper.rb#L27


Minitest::Retry.on_consistent_failure do |klass, test_name|
  Rails.logger.error("DO NOT IGNORE - Consistent failure - #{klass} #{test_name}")
end
Selenium::WebDriver::Chrome::Service.driver_path = ENV['TESTDRIVER_PATH'] || Foreman::Util.which('chromedriver', Rails.root.join('node_modules', '.bin'))
Capybara.register_driver :selenium_chrome do |app|
  options = Selenium::WebDriver::Chrome::Options.new
  options.args << '--disable-gpu'
  options.args << '--no-sandbox'
  options.args << '--window-size=1024,768'
  options.args << '--headless' unless ENV['DEBUG_JS_TEST'] == '1'
  Capybara::Selenium::Driver.new(app, browser: :chrome, options: options)
end
Capybara.configure do |config|
  config.javascript_driver      = ENV["JS_TEST_DRIVER"]&.to_sym || :selenium_chrome
  config.default_max_wait_time  = 20
end
class ActionDispatch::IntegrationTest
  # Make the Capybara DSL available in all integration tests
  include Capybara::DSL

However running tests yields in errors, nothing related to selenium works. All tags are not found.

lzap · June 14, 2021, 1:50pm

Question - when you run JS tests, do you see some arguments passed into chromedriver process? All I see is:

# ps axuwww | grep chrome
lzap     1791177  1.7  0.0 305872 22192 pts/6    Sl   15:49   0:00 /usr/bin/chromedriver --port=9515

I am wondering if arguments are actually passed in my case.

lzap · June 14, 2021, 1:52pm

Hmmm subprocesses do have the arguments.

lzap · June 15, 2021, 9:39am

I tried it on my laptop and it works there. But the error was different - it wanted me to run webpack:compile which I did not perform for quite some time on my main machine. Uh if this was it then I lost almost a day troubleshooting selenium-webdriver while it was simply missing compiled assets

lzap · June 15, 2021, 10:46am

That was indeed the case. Cool.