Add support for getting live stderr and stdout from the blimp client-engine integration script |
|||
Issue description
When using the script to {run} the engine implemented as part of issue 636410 , no output is printed.
###
$ ./out-engine/Debug/bin/client_engine_integration run
Blimp engine started
###
Even after a client connects, there is no output.
For local debugging it is incredibly helpful to get the console log from the engine.
Could you add a flag or something along those lines to get the log? Or maybe even be so bold as to make it the default when using {run} as the positional argument?
,
Aug 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8207e3a60214c97137ccb86ecd714a750124047c commit 8207e3a60214c97137ccb86ecd714a750124047c Author: shenghuazhang <shenghuazhang@chromium.org> Date: Fri Aug 12 18:25:25 2016 Add live output for blimp integration script {run} func Support for getting console log from the engine. Print the logs to stdout for {run} positional argument. BUG= 636410 Review-Url: https://codereview.chromium.org/2236143002 Cr-Commit-Position: refs/heads/master@{#411705} [modify] https://crrev.com/8207e3a60214c97137ccb86ecd714a750124047c/blimp/tools/client_engine_integration.py
,
Aug 15 2016
,
Dec 9 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by nyquist@chromium.org
, Aug 10 2016