Re: Issue 3003 in selenium: chromedriver.log location is hardcoded

[sele...@googlecode.com]

Comment #2 on issue 3003 by bino...@gmail.com: chromedriver.log location is
hardcoded
http://code.google.com/p/selenium/issues/detail?id=3003

I downloaded ChromeDriver v 18 from the downloads page and tried

chromedriver.exe -log-path=c:\users\me\desktop\chromedriver.log

or

chromedriver.exe --log-path=c:\users\me\desktop\chromedriver.log

i see that it stills generates the chromedriver.og in the current directory

did I use this switch right?

[sele...@googlecode.com]

Comment #3 on issue 3003 by bino...@gmail.com: chromedriver.log location is
hardcoded
http://code.google.com/p/selenium/issues/detail?id=3003

sorry, i take that back, i downloaded one older version, the latest version
fixes it for me :)

[sele...@googlecode.com]

Comment #4 on issue 3003 by hubert.c...@gmail.com: chromedriver.log

location is hardcoded
http://code.google.com/p/selenium/issues/detail?id=3003

Is it possible to include the --log-path switch when starting the
chromedriver from a remote selenium server? For example:

java -Dwebdriver.chrome.driver="/path/to/driver --log-path=/path/to/log"
-jar selenium-server-standalone.jar

[sele...@googlecode.com]

Comment #5 on issue 3003 by eli...@aclue.com: chromedriver.log location is
hardcoded
http://code.google.com/p/selenium/issues/detail?id=3003

Doesn't look like it:

Caused by: java.lang.IllegalStateException: The webdriver.chrome.driver
system property defined chromedriver executable does not exist:
/usr/bin/chromedriver --log-path=/path/to/log/chromedriver.log

Anyone have any ideas on this?

[sele...@googlecode.com]

Comment #6 on issue 3003 by kka...@google.com: chromedriver.log location is
hardcoded
http://code.google.com/p/selenium/issues/detail?id=3003

The fix added a command-line switch to chromedriver to allow a client to
specify the file, which is what the initial bug reporter initially wanted.
This can be used if you have direct control of running the chromedriver
process.

The 'webdriver.chrome.driver' system property for Java specifies the
location of the binary and not the command line string to use. I'm going to
leave this closed, but I opened a new bug for your request here:
http://code.google.com/p/selenium/issues/detail?id=3475

[sele...@googlecode.com]

Comment #7 on issue 3003 by kyle.qu...@gmail.com: chromedriver.log location
is hardcoded
http://code.google.com/p/selenium/issues/detail?id=3003

I was experiencing the issue of trying to load a local page via the command
driver.Url = @"file:///c:/path/to/local/file" and getting
data:text/html:charset=utf-8 in the address bar. My version of chrome was
26.i.can't.remember. The issue no longer occurring after an update of
Chrome. I am now running 27.0.1453.94 m.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings