jenkins - Protractor webdriver-manager takes forever to start Selenium -


i managed protractor tests running through jenkins build task on ci server, i'm having problem when run webdriver-manager start takes forever before selenium server starts.

eventually starts , console shows:

info - started socketlistener on 0.0.0.0:4444

but takes 5 minutes, whereas when try same on vagrant vm starts immediately.

i'm running headless protractor tests use xvfb-run run webdriver-manager start.

here's shell script use:

#!/bin/sh export display=:1  xvfb $display -ac -screen 0 1280x1024x8 & sleep 1  xvfb-run webdriver-manager start --standalone  

this starts selenium server on vagrant vm, takes long time on ci server. here's output of script on ci server:

jenkins@vps1:~/workspace/cms$ ./runwebdriver  initializing built-in extension generic event extension initializing built-in extension shape initializing built-in extension mit-shm initializing built-in extension xinputextension initializing built-in extension xtest initializing built-in extension big-requests initializing built-in extension sync initializing built-in extension xkeyboard initializing built-in extension xc-misc initializing built-in extension security initializing built-in extension xinerama initializing built-in extension xfixes initializing built-in extension render initializing built-in extension randr initializing built-in extension composite initializing built-in extension damage initializing built-in extension mit-screen-saver initializing built-in extension double-buffer initializing built-in extension record initializing built-in extension dpms initializing built-in extension present initializing built-in extension dri3 initializing built-in extension x-resource initializing built-in extension xvideo initializing built-in extension xvideo-motioncompensation initializing built-in extension selinux initializing built-in extension glx jenkins@vps1:~/workspace/cms$ seleniumprocess.pid: 27952 21:21:21.633 info - launching standalone server setting system property webdriver.chrome.driver /var/lib/jenkins/.nvm/versions/io.js/v2.0.2/lib/node_modules/protractor/selenium/chromedriver 21:21:21.760 info - java: oracle corporation 24.79-b02 21:21:21.760 info - os: linux 3.13.0-53-generic amd64 21:21:21.810 info - v2.45.0, core v2.45.0. built revision 5017cb8 21:21:21.960 info - default driver org.openqa.selenium.ie.internetexplorerdriver registration skipped: registration capabilities capabilities [{platform=windows, ensurecleansession=true, browsername=internet explorer, version=}] not match current platform: linux 21:21:22.108 info - remotewebdriver instances should connect to: http://127.0.0.1:4444/wd/hub 21:21:22.109 info - version jetty/5.1.x 21:21:22.111 info - started httpcontext[/selenium-server/driver,/selenium-server/driver] 21:21:22.112 info - started httpcontext[/selenium-server,/selenium-server] 21:21:22.112 info - started httpcontext[/,/] <-- hangs 

after minutes runs , can execute protractor tests, annoying , not suitable running tests on ci server.

on vagrant vm selenium server starts , output identical point:

19:47:08.507 info - java: oracle corporation 24.65-b04 19:47:08.509 info - os: linux 3.13.0-44-generic amd64 19:47:08.536 info - v2.45.0, core v2.45.0. built revision 5017cb8 19:47:08.663 info - default driver org.openqa.selenium.ie.internetexplorerdriver registration skipped: registration capabilities capabilities [{platform=windows, ensurecleansession=true, browsername=internet explorer, version=}] not match current platform: linux 19:47:08.760 info - remotewebdriver instances should connect to: http://127.0.0.1:4444/wd/hub 19:47:08.762 info - version jetty/5.1.x 19:47:08.763 info - started httpcontext[/selenium-server/driver,/selenium-server/driver] 19:47:08.764 info - started httpcontext[/selenium-server,/selenium-server] 19:47:08.765 info - started httpcontext[/,/] 19:47:08.800 info - started org.openqa.jetty.jetty.servlet.servlethandler@14b43af3 19:47:08.801 info - started httpcontext[/wd,/wd] 19:47:08.807 info - started socketlistener on 0.0.0.0:4444 19:47:08.808 info - started org.openqa.jetty.jetty.server@16692a88 

both machines run ubuntu 14.04 kernel version , version of java different (see output), protractor version on ci server 2.1.0, on vm 1.8.0.

could problem or missing here?

the issue seems related source of randomness selenium using.

more info here: https://code.google.com/p/selenium/issues/detail?id=1301

tl;dr solution: append -djava.security.egd=file:///dev/urandom java command launches selenium. may have edit webdriver-manager's config.


Comments

Popular posts from this blog

angularjs - ADAL JS Angular- WebAPI add a new role claim to the token -

php - CakePHP HttpSockets send array of paramms -

node.js - Using Node without global install -