I am launching the node using this command which is successful, but not generating logs.
FYI- I created the folder "C:\webdriver\IE.log" on the node,but it is not generating log as the log file is @0kb.
Please suggest how to launch the node that generates log file.
java -jar selenium-server-standalone-2.39.0.jar -Xms=256m
-role node
-Dwebdriver.chrome.driver="C:\Chromedriver\chromedriver.exe"
-Dwebdriver.ie.driver="C:\IEdriver\IEDriverServer.exe"
--log-level=TRACE --log-file="C:\webdriver\IE.log" -nodeConfig
nodeConfig.json -Xmx=512m
Reason i am doing this is - I am getting this error "internet explorer has stopped working" on Windows 7 and IE11.0 and 2.39.0 of webdriver with 32 bit IEserver of 2.39.0
1.I tried resetting the browser with default settings that didn't work and other browser setttings ,but no luck.
Please help
java -jar selenium-server-standalone-2.39.0.jar -Xms=256m
-role node
-Dwebdriver.chrome.driver="C:\Chromedriver\chromedriver.exe"
-Dwebdriver.ie.driver="C:\IEdriver\IEDriverServer.exe" -Dwebdriver.ie.driver.loglevel=TRACE -Dwebdriver.ie.driver.logfile="C:\webdriver\IE.log" -nodeConfig
nodeConfig.json -Xmx=512m
This information can be found in the project wiki at https://code.google.com/p/selenium/wiki/InternetExplorerDriver.
Let me caution you, however. If you're considering opening an issue in the tracker, having only the logs to share (and not a sample website to repro the issue against), your issue report will get no attention, aside from asking for a repro case.
"internet explorer has stopped working" on Windows 7 and IE11.0 and 2.39.0 of webdriver with 32 bit IEserver of 2.39.0
--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webdriver+...@googlegroups.com.
To post to this group, send email to webd...@googlegroups.com.
Visit this group at http://groups.google.com/group/webdriver.
For more options, visit https://groups.google.com/d/optout.
--Jim
[1] https://code.google.com/p/selenium/issues/detail?id=7021#c10
--
--
Here's the thing: the HTML DOM is a very complex thing. The same WebDriver code can produce vastly different results for differently structures pages, so the log alone, while helpful, is insufficient for accurate diagnosis. And there are nearly infinite edge cases, so it's frankly unrealistic to expect the WebDriver team to be able to a priori anticipate them all. So a test page is absolutely critical to resolving any issue of this type.
Note that so-called "intermittent" test failures can often be reproduced by running a test case in a loop for, say, 100 times. If you are unwilling to provide a test page[1], there's very little that can be done to resolve the issue.
--Jim
[1] Yes, I used the word "unwilling" on purpose. Those who claim to be "unable" to provide a test page usually invoke one of the Evans Bogus Reasons for not doing so. See http://jimevansmusic.blogspot.com/2012/12/not-providing-html-page-is-bogus.html if this attitude seems excessively strident to you.