Unable to get chrome logs
See original GitHub issueI’m trying to get chrome’s logs when launched through WebdriverIO. These are the options I use to start chrome with:
{
desiredCapabilities: {
browserName: 'chrome',
chromeOptions: {
binary: path.resolve('/usr/bin/google-chrome'),
forceDevToolsScreenshot: true,
args: [
'--load-and-launch-app=' + path.resolve('./build/chrome/'),
'--enable-logging',
'--v=1',
'--no-sandbox',
]
}
}
}
When I run my script through Mocha, Chrome (and the external app) launches, but I do not see a chrome_debug.log file in my user directory (which should be ~/.config/google-chrome/
if I’m not mistaken).
If I do the same manually, as in, launching chrome via the command line google-chrome --enable-logging --v=1
, the file does indeed appear, which leads me to believe this might be an issue with WebdriverIO.
I’m using Ubuntu 14.04 (Chrome 48), but I’ve tried doing the same on OSX(Chrome 49), with the same result.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Chrome Browser debug logs - Google Support
You can troubleshoot problems with Chrome Browser, such as hanging tabs and error messages. Use debug logs to help you. These logs aren't...
Read more >How to Find Error Logs to Troubleshoot Chrome Issues
Open the Terminal and run the following command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1. Press ...
Read more >Unable to get Chrome Performance logs in Selenium C# ...
Chrome.WebDriver (v79.0.0) and using the following code, I am able to retrieve the performance logs. ChromeOptions options = new ChromeOptions ...
Read more >Getting chromedriver.log when you run Record/Spy Web to ...
Hope this helps. 5 Likes. I can not start Chrome from Katalon. Chrome Driver, unable to navigate.
Read more >Unable to log to chrome_debug.log in headless mode
Logging was recently fixed to match the behavior of non-headless Chrome, so you should find the log file in expected location. - Sami....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this is something that needs to be fixed in the chromedriver project.
If I set CHROME_LOG_FILE to a filename before running wdoi, then Chrome writes the log to the filename. (If I don’t set CHROME_LOG_FILE, then it doesn’t seem like Chrome writes its log file anywhere, which isn’t consistent with the behavior I get from just launching Chrome with --enable-logging.)