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

kill: invalid option -- '9' #44

Open
map7 opened this issue Jul 15, 2015 · 0 comments
Open

kill: invalid option -- '9' #44

map7 opened this issue Jul 15, 2015 · 0 comments

Comments

@map7
Copy link
Contributor

map7 commented Jul 15, 2015

I'm getting this error after running protractor through protractor-rails rake task like so

bundle exec rake protractor:spec nolog=y

Error I get;

kill protractor rails tests server...
kill webdriver server...
[2015-07-15 15:25:42] FATAL SignalException: SIGTERM
    /usr/local/rbenv/versions/2.1.5/lib/ruby/2.1.0/webrick/server.rb:170:in `select'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/2.1.0/webrick/server.rb:170:in `block in start'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/2.1.0/webrick/server.rb:32:in `start'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/2.1.0/webrick/server.rb:160:in `start'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rack-1.4.7/lib/rack/handler/webrick.rb:13:in `run'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rack-1.4.7/lib/rack/server.rb:268:in `start'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/railties-3.2.21/lib/rails/commands/server.rb:70:in `start'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/railties-3.2.21/lib/rails/commands.rb:55:in `block in <top (required)>'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/railties-3.2.21/lib/rails/commands.rb:50:in `tap'
    /usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/railties-3.2.21/lib/rails/commands.rb:50:in `<top (required)>'
    script/rails:6:in `require'
    script/rails:6:in `<main>'
[2015-07-15 15:25:42] INFO  going to shutdown ...
[2015-07-15 15:25:42] INFO  WEBrick::HTTPServer#start done.
Exiting

kill left over selenium processes...
Selenium Standalone has exited with code null
kill: invalid option -- '9'

Usage:
 kill [options] <pid> [...]

Options:
 <pid> [...]            send signal to every <pid> listed
 -<signal>, -s, --signal <signal>
                        specify the <signal> to be sent
 -l, --list=[<signal>]  list all signal names, or convert one to a name
 -L, --table            list all signal names in a nice table

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see kill(1).
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