headless and remote debugger logs to stderr instead of stdout
Reported by
br...@dockyard.com,
Oct 11 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.45 Safari/537.36 Steps to reproduce the problem: 1. start headless with `chrome --headless --remote-debugging-port=9222 --disable-gpu` 2. Chrome should output a message indicating that devtools has booted and a URLto access 3. close chrome 4. start headless but send stderr output to /dev/null: `chrome --headless --remote-debugging-port=9222 --disable-gpu 2> /dev/null` 5. There isn't any output logged, but the chrome instance has started. This indicates that messages that are meant for stdout are being sent to stderr by mistake What is the expected behavior? I would expect that stdout should be used for logging and general non-error status messages What went wrong? Chrome is using stderr for messages that are not errors Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3202.45 Channel: beta OS Version: OS X 10.12.6 Flash Version:
,
Oct 15 2017
I think this is WAI, It's same behavior with non-headless Chrome, so we shouldn't do anything different
,
Oct 15 2017
> I think this is WAI I'm not sure what WAI means. Also, why would sending non-error messages to stderr be OK? Other consuming programs depend upon sensical output levels.
,
Oct 16 2017
Sorry, WAI == Working as Intended, as of we are doing the same as Chrome non-headless. If you want to change the behavior it should be done for both headless and non-headless Chrome, feel free to create a feature request for that |
||
►
Sign in to add a comment |
||
Comment 1 by rsesek@chromium.org
, Oct 11 2017