Add more command line feedback to debugd such we can gather more info in user feedback |
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8350.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.85 Safari/537.36 Steps to reproduce the problem: Usually we use the shortcut key Alt-Shift-i to file user feedback when we encounter any issues. What is the expected behavior? What went wrong? We need more info to be in the feedback report. For example, when we deal with the samus performance bug, we need to use some pattern to verify performance issue, such as top's thread mode or perf record. Did this work before? N/A Chrome version: Channel: dev OS Version: 8350.60.0 Flash Version: Shockwave Flash 22.0 r0
,
Aug 9 2016
,
Aug 9 2016
,
Aug 9 2016
Ahmed, I remembered you noticed a place where we might truncate the content of the feedback report. Could you add some pointer here so that we can take care of it too?
,
Aug 9 2016
I'm currently the owner of the feedback app, so let me know what extra info you want to add. Regarding the truncated sys info, I recently fixed that bug in Issue 634518 . system_logs.zip should contain everything now.
,
Aug 10 2016
Hi Ahmed, We were planning for adding two sources of the system info into the feedback report for diagnosing performance issues. The first one is the 'thread mode' top which provides better understanding of how the processors are used. (I sent this: https://chromium-review.googlesource.com/#/c/367160/ ). The second one is to provide an option for the user to send a 10-seconds perf record data. The former is easier and straightforward but the latter might involve some ui change. What do you think ?
,
Aug 10 2016
For UI changes, we have to go through UI review. For the first change, yes, absolutely. Thanks!
,
Aug 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/4210f3c955b8dbb6c885fc5caa6afb50f7a55165 commit 4210f3c955b8dbb6c885fc5caa6afb50f7a55165 Author: Hsu-Cheng Tsai <hctsai@google.com> Date: Fri Aug 05 02:50:19 2016 debugd: Add top (thread mode) to user feedback. BUG= chromium:635415 TEST=manual Change-Id: I687278bf1410e9043db5557b0c0705cd858baffe Reviewed-on: https://chromium-review.googlesource.com/367160 Commit-Ready: Hsu-Cheng Tsai <hctsai@chromium.org> Tested-by: Hsu-Cheng Tsai <hctsai@chromium.org> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> [modify] https://crrev.com/4210f3c955b8dbb6c885fc5caa6afb50f7a55165/debugd/src/log_tool.cc
,
Aug 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/4210f3c955b8dbb6c885fc5caa6afb50f7a55165 commit 4210f3c955b8dbb6c885fc5caa6afb50f7a55165 Author: Hsu-Cheng Tsai <hctsai@google.com> Date: Fri Aug 05 02:50:19 2016 debugd: Add top (thread mode) to user feedback. BUG= chromium:635415 TEST=manual Change-Id: I687278bf1410e9043db5557b0c0705cd858baffe Reviewed-on: https://chromium-review.googlesource.com/367160 Commit-Ready: Hsu-Cheng Tsai <hctsai@chromium.org> Tested-by: Hsu-Cheng Tsai <hctsai@chromium.org> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> [modify] https://crrev.com/4210f3c955b8dbb6c885fc5caa6afb50f7a55165/debugd/src/log_tool.cc
,
Jan 12 2017
We don't have plan to add new commands in near future yet while 'perf record' is still an option.
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Jun 20 2017
Verified in Chrome OS 9667.0.0, 61.0.3130.0. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sheriffbot@chromium.org
, Aug 8 2016