You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently deploying this module to a customer who is using Behat with PhantomJS to test his application, and we're been running into the following issue, under Puppet 3.4, Ubuntu 14.04 and selenium-server-standalone 2.45.0:
Whenever the test suite is started, an obscure and unhelpful error arises and it is unable to continue.
After some digging around using strace, I managed to pin down the issue to the selenium-standalone daemon trying to create /phantomjsdriver.log and failing to do so because of permission issues.
We managed to workaround the issue by editing the /etc/init.d/seleniumserver initscript's DAEMON_ARGS variable: adding --chdir=/var/lib/selenium ensures that the daemon is creating all its files in a directory its has write access to.
Are you able to reproduce this issue?
The text was updated successfully, but these errors were encountered:
Hi,
I'm currently deploying this module to a customer who is using Behat with PhantomJS to test his application, and we're been running into the following issue, under Puppet 3.4, Ubuntu 14.04 and selenium-server-standalone 2.45.0:
Whenever the test suite is started, an obscure and unhelpful error arises and it is unable to continue.
After some digging around using
strace
, I managed to pin down the issue to the selenium-standalone daemon trying to create/phantomjsdriver.log
and failing to do so because of permission issues.We managed to workaround the issue by editing the
/etc/init.d/seleniumserver
initscript'sDAEMON_ARGS
variable: adding--chdir=/var/lib/selenium
ensures that the daemon is creating all its files in a directory its has write access to.Are you able to reproduce this issue?
The text was updated successfully, but these errors were encountered: