We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In issue #473, it appears we'd be able to get more information if allow developers to pass custom options to on chromedriver startup.
Below are the options needed to get the chromedriver debug info written to a log file
--log-level=DEBUG --log-path=/path/to/log/chomedriver.log --port=<port>
By starting chromedriver with these options, we're able to get more helpful error output like this:
[1581199532.142][DEBUG]: DevTools WebSocket Event: Runtime.exceptionThrown 928486C2388B88595FC1D7B4B910AFC3 { "exceptionDetails": { "columnNumber": 8, "exception": { "type": "string", "value": "Test Error" }, "exceptionId": 1, "executionContextId": 1, "lineNumber": 15, "stackTrace": { "callFrames": [ { "columnNumber": 8, "functionName": "throwError", "lineNumber": 15, "scriptId": "4", "url": "http://localhost:32929/errors.html" } ] }, "text": "Uncaught", "url": "http://localhost:32929/errors.html" }, "timestamp": 1.581199532141929e+12 }
The text was updated successfully, but these errors were encountered:
aaronrenner
No branches or pull requests
In issue #473, it appears we'd be able to get more information if allow developers to pass custom options to on chromedriver startup.
Below are the options needed to get the chromedriver debug info written to a log file
By starting chromedriver with these options, we're able to get more helpful error output like this:
The text was updated successfully, but these errors were encountered: