I am using watir-webdriver and getting this error message when opening a chrome browser:
C:\chromeDriver>irb
DL is deprecated, please use Fiddle
irb(main):001:0> require "watir-webdriver"
=> true
irb(main):002:0> a = Watir::Browser.new (:chrome)
Started ChromeDriver
port=9515
version=0.8
log=C:\chromeDriver\chromedriver.log
Selenium::WebDriver::Error::UnknownError: unknown error: unrecognized chrome option:
detach
(Driver info: chromedriver=0.8,platform=Windows NT 6.2 x86_64)
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/response.rb:51:in `assert_ok'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/response.rb:15:in `initialize'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/common.rb:59:in `new'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/common.rb:59:in `create_response'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/default.rb:66:in `request'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/http/common.rb:40:in `call'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/bridge.rb:629:in `raw_execute'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/bridge.rb:98:in `create_session'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/remote/bridge.rb:68:in `initialize'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/chrome/bridge.rb:29:in `initialize'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/common/driver.rb:37:in `new'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver/common/driver.rb:37:in `for'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/selenium-webdriver-2.33.0/lib/selenium/webdriver.rb:67:in `for'
from C:/Ruby200/lib/ruby/gems/2.0.0/gems/watir-webdriver-0.6.4/lib/watir-webd river/browser.rb:46:in `initialize'
from (irb):2:in `new'
from (irb):2
Environment:
Windows 8
Ruby version = ruby 2.0.0p247 (2013-06-27) [i386-mingw32]
Based on the exception, you are using selenium-webdriver version 2.33.0. My guess is there is an incompatibility between this version and your chromedriver.
Assuming you are using the latest chromedriver, you likely need to update to the latest selenium-webdriver, which is version 2.35.1.
Try a:
gem install selenium-webdriver
Download the new chrome driver
http://chromedriver.storage.googleapis.com/index.html?path=2.4/
I was having the same issue and updated the chrome driver, and the issue was resolved. I also updated my gems.
Related
I am getting this error while Building New Rails App with PostgreSQL please help:
Fetching gem metadata from https://rubygems.org/...........
Resolving dependencies...
Using rake 13.0.6
Using concurrent-ruby 1.1.10
Using websocket-extensions 0.1.5
Using marcel 1.0.2
Using mini_mime 1.1.2
Using digest 3.1.0
Using timeout 0.3.0
Using minitest 5.16.2
Using public_suffix 4.0.7
Using crass 1.0.6
Using rack 2.2.4
Using bundler 2.3.17
Using erubi 1.11.0
Using racc 1.6.0
Using strscan 3.0.4
Using bindex 0.8.1
Using io-console 0.5.11
Using nio4r 2.5.8
Using builder 3.2.4
Using matrix 0.4.2
Using regexp_parser 2.5.0
Using childprocess 4.1.0
Using method_source 1.0.0
Using msgpack 1.5.4
Using thor 1.2.1
Using zeitwerk 2.6.0
Using redis 4.7.1
Using rexml 3.2.5
Using net-protocol 0.1.3
Using addressable 2.8.0
Using i18n 1.12.0
Using tzinfo 2.0.5
Using websocket-driver 0.7.5
Using mail 2.7.1
Using rubyzip 2.3.2
Using websocket 1.2.9
Using rack-test 2.0.2
Using sprockets 4.1.1
Using nokogiri 1.13.8 (x86_64-linux)
Using net-smtp 0.3.1
Using reline 0.3.1
Using bootsnap 1.13.0
Using net-imap 0.2.3
Using xpath 3.2.0
Using irb 1.4.1
Using puma 5.6.4
Using debug 1.6.1
Using loofah 2.18.0
Using net-pop 0.1.1
Using activesupport 7.0.3.1
Using capybara 3.37.1
Using globalid 1.0.0
Using rails-html-sanitizer 1.4.3
Using selenium-webdriver 4.3.0
Using rails-dom-testing 2.0.3
Using webdrivers 5.0.0
Using actionview 7.0.3.1
Using activemodel 7.0.3.1
Using activejob 7.0.3.1
Using activerecord 7.0.3.1
Using jbuilder 2.11.5
Using actionpack 7.0.3.1
Using activestorage 7.0.3.1
Using actionmailer 7.0.3.1
Using actionmailbox 7.0.3.1
Using actiontext 7.0.3.1
Using sprockets-rails 3.4.2
Using actioncable 7.0.3.1
Using railties 7.0.3.1
Using rails 7.0.3.1
Using turbo-rails 1.1.1
Using importmap-rails 1.1.5
Using web-console 4.2.0
Using stimulus-rails 1.1.0
Installing pg 1.4.2 with native extensions
Bundler::DirectoryRemovalError: Could not delete previous installation of
`/var/lib/gems/2.7.0/gems/pg-1.4.2`.
The underlying error was Errno::EACCES: Permission denied # dir_s_rmdir -
/var/lib/gems/2.7.0/gems/pg-1.4.2/sample, with backtrace:
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1459:in
`rmdir'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1459:in
`block in remove_dir1'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1470:in
`platform_support'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1458:in
`remove_dir1'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1451:in
`remove'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:780:in
`block in remove_entry'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1503:in
`block (2 levels) in postorder_traverse'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1508:in
`ensure in postorder_traverse'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1508:in
`postorder_traverse'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1502:in
`block in postorder_traverse'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1501:in
`each'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:1501:in
`postorder_traverse'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:778:in
`remove_entry'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/vendor/fileutils/lib/fileutils.rb:698:in
`remove_entry_secure'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler.rb:331:in `rm_rf'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/rubygems_gem_installer.rb:104:in
`strict_rm_rf'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/rubygems_gem_installer.rb:19:in
`install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/source/rubygems.rb:209:in
`install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/gem_installer.rb:54:in
`install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/gem_installer.rb:16:in
`install_from_spec'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/parallel_installer.rb:186:in
`do_install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/parallel_installer.rb:177:in
`block in worker_pool'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:62:in
`apply_func'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:57:in `block in
process_queue'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:54:in `loop'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:54:in
`process_queue'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:91:in `block (2
levels) in create_threads'
Bundler Error Backtrace:
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/rubygems_gem_installer.rb:106:in
`rescue in strict_rm_rf'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/rubygems_gem_installer.rb:103:in
`strict_rm_rf'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/rubygems_gem_installer.rb:19:in
`install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/source/rubygems.rb:209:in
`install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/gem_installer.rb:54:in
`install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/gem_installer.rb:16:in
`install_from_spec'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/parallel_installer.rb:186:in
`do_install'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/installer/parallel_installer.rb:177:in
`block in worker_pool'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:62:in
`apply_func'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:57:in `block in
process_queue'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:54:in `loop'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:54:in
`process_queue'
/var/lib/gems/2.7.0/gems/bundler-2.3.17/lib/bundler/worker.rb:91:in `block (2
levels) in create_threads'
An error occurred while installing pg (1.4.2), and Bundler cannot
continue.
In Gemfile:
pg
I am using Arctic Fox 2020.3.1 (ARM version- designed for Apple silicon), on Macbook Air M1 2020 model, running flutter project. I am successfully able to run on Android emulator, but when i try to run on attached iOS device or iOS simulator "pod install" command fails and build failed. But when i open my terminal on rosetta 2 and try "pod install" manually it install all pods, and after that i am able to run the build from XCODE but not from Android Studio, so my question is: Is terminal inside Android Studio runs on Apple (not on rosetta 2) that's why it fails.
Note: I have changed the configuration of terminal to run it forcefully on rosetta 2.
This happens when i try to run for ios from studio
The plugins `flutter_full_pdf_viewer, flutter_webview_plugin, onesignal_flutter` use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.
Launching lib/main.dart on Lakhwinder’s iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: E942NB2Q9L
Running pod install...
CocoaPods' output:
↳
CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
Error output from CocoaPods:
↳
WARNING: CocoaPods requires your terminal to be using UTF-8 encoding.
Consider adding the following to ~/.profile:
export LANG=en_US.UTF-8
/opt/homebrew/Cellar/ruby/3.0.2/lib/ruby/3.0.0/unicode_normalize/normalize.rb:141:in `normalize': Unicode Normalization not appropriate for ASCII-8BIT (Encoding::CompatibilityError)
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `unicode_normalize'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `installation_root'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:226:in `podfile_path'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/user_interface/error_report.rb:105:in `markdown_podfile'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/user_interface/error_report.rb:30:in `report'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:66:in `report_error'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:396:in `handle_exception'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:337:in `rescue in run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:324:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `load'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `<main>'
/opt/homebrew/Cellar/ruby/3.0.2/lib/ruby/3.0.0/unicode_normalize/normalize.rb:141:in `normalize': Unicode Normalization not appropriate for ASCII-8BIT (Encoding::CompatibilityError)
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `unicode_normalize'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:166:in `installation_root'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:226:in `podfile_path'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/config.rb:205:in `podfile'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:160:in `verify_podfile_exists!'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command/install.rb:46:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `load'
from /opt/homebrew/Cellar/cocoapods/1.11.2/libexec/bin/pod:23:in `<main>'
Exception: Error running pod install
open Terminal type open ~/.zshrc (or .profile if you don't use zsh)
It seems that LANG="en_US.UTF-8" alone isn't enough, you have to set
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
export LC_ALL=en_US.UTF-8
save the file
go back to Terminal
type source ~/.zshrc
type locale
You can now safely run pod update or pod install
You may have to install ffi. Run sudo gem install ffi then normal flutter run should work as expected.
When I clone the project from https://github.com/daattali/beautiful-jekyll.git on my computer, I use jekyll serve to start the project, but it will some error, what should I do if I want to Local development using jekyll?
the error is:
WARN: Unresolved specs during Gem::Specification.reset:
jekyll-watch (~> 1.1)
rouge (< 3, >= 1.7)
rb-fsevent (>= 0.9.4, ~> 0.9)
rb-inotify (>= 0.9.7, ~> 0.9)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/runtime.rb:313:in `check_for_activated_spec!': You have already activated public_suffix 3.0.1, but your Gemfile requires public_suffix 2.0.5. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/runtime.rb:31:in `block in setup'
from C:/Ruby24-x64/lib/ruby/2.4.0/forwardable.rb:229:in `each'
from C:/Ruby24-x64/lib/ruby/2.4.0/forwardable.rb:229:in `each'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler/runtime.rb:26:in `map'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-`enter code here`1.16.0/lib/bundler/runtime.rb:26:in `setup'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/bundler-1.16.0/lib/bundler.rb:107:in `setup'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-3.6.2/lib/jekyll/plugin_manager.rb:50:in `require_from_bundler'
from C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/jekyll-3.6.2/exe/jekyll:11:in `<top (required)>'
from C:/Ruby24-x64/bin/jekyll:23:in `load'
from C:/Ruby24-x64/bin/jekyll:23:in `<main>'
I have solved my question.
First: you should add the code to your Gemfile file.
the code is
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
Then: you use bundle exec jekyll serve to start. After that you can use local development.
I'm working on my Github Pages site, so need to build it on my local machine. Following their instructions, I have set it up using bundler. However bundler appears to break the Jekyll build.
If I run jekyll new NewSite it creates a new site that can be built using jekyll serve. As soon as I run bundle install, or bundle update, however, Jekyll refuses to run, giving the below error on the "generating" step.
jekyll 3.0.5 | Error: No such file or directory - git remote --verbose
It will then give that same error every time either bundle exec jekyll serve or jekyll serve are called. Further investigation has found that the error goes away if the gemfile file is deleted.
What have I misconfigured?
Update:
I've added a stack trace as requested
I realised it was the gemfile itself that was causing the issue, not the gemfile.lock
Problem turned out to have nothing to do with Windows, so removed references to it
Stack trace:
C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:32
:in ``': No such file or directory - git remote --verbose (Errno::ENOENT)
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:32:in `git_remote_url'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:39:in `nwo_from_git_origin_remote'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:65:in `nwo'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-github-metadata-1.11.1/lib/jekyll-github-metadata/ghp_metadata_generator.rb:8:in `generate'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:154:in `block in generate'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:153:in `each'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:153:in `generate'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/site.rb:58:in `process'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/command.rb:28:in `process_site'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/commands/build.rb:60:in `build'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/commands/build.rb:35:in `process'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/lib/jekyll/commands/serve.rb:26:in `block (2 levels) in init_with_program'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `call'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
from C:/Ruby22/lib/ruby/gems/2.2.0/gems/jekyll-3.0.5/bin/jekyll:17:in `<top (required)>'
from C:/Ruby22/bin/jekyll:23:in `load'
from C:/Ruby22/bin/jekyll:23:in `<main>'
My Gemfile:
source 'https://rubygems.org'
gem 'github-pages', group: :jekyll_plugins
gem 'safe_yaml', '~> 1.0.4'
gem 'wdm', '~> 0.1.0' if Gem.win_platform?
Ruby version: 2.2.4 32 bit
Bundler version: 1.12.3
Jekyll Version: 3.0.5
This is jekyll-github-metadata gem which is bugging when trying to run a git remote --verbose command on your system (code).
You can try to set a _config.yml variable (documentation) :
repository: username/repo-name
Problem: When I run my tests, I get the following message in the command prompt
Started ChromeDriver
port=9515
version=21.0.1180.4
log=C:\Users\jhomer\Desktop\Workspace\WebAutomationTesting\Tests\chromedriver.log
Chrome then starts, after which I get a windows error message stating the chromedriver has stopped working.
Additional Information:
I just recently switched from a mac (osx) to windows 7. I'm using the same IDE (Aptana 3) and I have installed the same gems:
addressable (2.2.8)
bigdecimal (1.1.0)
builder (3.0.0)
childprocess (0.3.2)
commonwatir (3.0.0)
ffi (1.0.11)
hoe (3.0.6)
io-console (0.3)
json (1.7.3, 1.5.4)
json_pure (1.7.3)
libwebsocket (0.1.3)
minitest (3.2.0, 3.1.0, 2.5.1
multi_json (1.3.6)
nokogiri (1.5.5 x86-mingw32)
rake (0.9.2.2)
rautomation (0.7.2)
rdoc (3.12, 3.9.4)
rubygems-update (1.8.24)
rubyzip (0.9.9)
s4t-utils (1.0.4)
selenium-webdriver (2.24.0)
user-choices (1.1.6.1)
watir (3.0.0)
watir-classic (3.0.0)
watir-webdriver (0.6.1)
win32-api (1.4.8 x86-mingw32)
win32-process (0.6.5)
windows-api (0.4.1)
windows-pr (1.2.1)
xml-simple (1.1.1)
I have run gem update, gem pristine --all, none of which have helped.
** update **
The error I was getting on the prompt after the tests "completed" is as follows:
So before I used the version you suggested I was getting this error:
Error:
test_UserRoles(UserRolesTest):
Errno::ECONNREFUSED: No connection could be made because the target machine actively refused it. - connect(2)
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/remote/http/default.rb:76:in `response_for'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/remote/http/default.rb:38:in 'request'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/remote/http/common.rb:40:in `call'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/remote/bridge.rb:598:in 'raw_execute'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/remote/bridge.rb:576:in `execute'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/remote/bridge.rb:189:in 'quit'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/chrome/bridge.rb:48:in 'quit'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.24.0/lib/selenium/w ebdriver/common/driver.rb:166:in `quit'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-webdriver-0.6.1/lib/watir-webdrive r/browser.rb:87:in 'close'
UserRolesTest.rb:48:in 'teardown'
Let me know if there is any additional information you may require.
Thanks.
I had the same problem and had to downgrade the chromedriver to version 20 (May 23). It works fine for me now on Windows 7 x64. Here's the download link.
It seems that the windows version of chromedriver crashes when the .close method is called on the browser. That was the problem. Is there another method for closing the browser upon finishing the tests?