Issue metadata
Sign in to add a comment
|
ninja_log visualization is broken |
||||||||||||||||||||||
Issue descriptionOpen any bot's compile stdout, and scroll to the end. There's a link saying "Visualization at http://chromium-build-stats.appspot.com/ninja_log/2016/04/21/slave4-c1/ninja_log.slave4-c1.chrome-bot.20160421-123954.22271.gz" or similar. Click "Trace Viewer". Expected: Trace with compile timings. Actual: No trace shows up, instead a single line of garbled text appears. This used to work.
,
Apr 27 2016
fixed, with CL in review https://codereview.chromium.org/1916363002/
,
Apr 27 2016
hmm, not yet? got import error..
,
Apr 27 2016
anyway, table would be available. http://chromium-build-stats.appspot.com/ninja_log/2016/04/21/slave4-c1/ninja_log.slave4-c1.chrome-bot.20160421-123954.22271.gz/table
,
Apr 27 2016
downloading trace.json and loading it in chrome://tracing works.
,
Apr 27 2016
ah, I deployed from wrong branch. deployed with https://codereview.chromium.org/1916363002/ and now trace view works fine.
,
Apr 27 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by thakis@chromium.org
, Apr 26 2016