Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest docker image does not seem to work at all #543

Closed
2 of 3 tasks
jimbobhickville opened this issue Nov 6, 2017 · 1 comment
Closed
2 of 3 tasks

Latest docker image does not seem to work at all #543

jimbobhickville opened this issue Nov 6, 2017 · 1 comment

Comments

@jimbobhickville
Copy link
Contributor

The latest version of the docker image on docker hub is failing with a missing shared library problem:

/.chromedriver-helper/2.33/linux64/chromedriver: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
/usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/lib/wraith/helpers/utilities.rb:58:in `run_command_safely': undefined method `chomp' for nil:NilClass (NoMethodError)
	from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/lib/wraith/helpers/utilities.rb:36:in `list_debug_information'
	from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/lib/wraith/validate.rb:14:in `validate'
	from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/lib/wraith/cli.rb:145:in `block in history'
	from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/lib/wraith/helpers/utilities.rb:4:in `within_acceptable_limits'
	from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/lib/wraith/cli.rb:144:in `history'
	from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
	from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-4.2.0/bin/wraith:5:in `<top (required)>'
	from /usr/local/bin/wraith:23:in `load'
	from /usr/local/bin/wraith:23:in `<main>'

Everything was working fine last week with the same configs.


Reporting a problem? Please describe the issue above, and complete the following checklist so that we can help you more quickly.

Issue checklist:

  • I have validated my config file against YAML Validator to make sure it is valid YAML.

  • [] I have run the wraith info command and pasted the output below:

paste results here
  • I have run the command in verbose mode (by adding verbose: true to my config) and pasted the output below:
paste results here
  • I have pasted the contents of my config file below:
---
browser: "phantomjs"
phantomjs_options: "--ignore-ssl-errors=true"
domains:
  current: https://regression-redis-test.mwcprodtest.com
imports: "regression_paths.yaml"
screen_widths:
  - 1280
resize_or_reload: 'resize'
history_dir: 'shots_base'
directory: 'shots'
fuzz: '20%'
threshold: 0
gallery:
  template: 'slideshow_template' # Examples: 'basic_template' (default), 'slideshow_template'
  thumb_width:  200
  thumb_height: 200
mode: diffs_first
verbose: true
highlight_color: red

The included regression_paths.yaml is:

 ---
"paths":
  "category": "/category/uncategorized/"
  "home": "/"
  "post": ""
@jimbobhickville
Copy link
Contributor Author

Trying to run wraith info in the container throws the same error. If you apt-get install libnss3-dev libgconf-2-4 the problem goes away. I'm testing a forked image now to see if it solves the original bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant