Issue metadata
Sign in to add a comment
|
chrome://net-internals#chromeos regression: debug log file is missing "tar.gz" extension |
||||||||||||||||||||||||
Issue descriptionchrome://net-internals#chromeos used a generate a log file with the name "debug-logs-<timestamp>.tar.gz". Recently the tar.gz extension is missing, meaning its harder to extract/view logs on a chromebook / non-Linux-desktop.
,
Oct 30 2017
,
Oct 30 2017
,
Feb 3 2018
This is a regression and has been in the field for 2-3 releases now. Customers/OEMs get confused and zip up the resulting filename and send to us. Can we please get some cycles on this?
,
Mar 2 2018
Ha, I've been wondering why partners send me really stupid-looking zipped-up tarballs with no extension...now I know! And unfortunately, it's our own fault :( https://chromium-review.googlesource.com/599026 + base::FilePath new_path = base_path; + // Assume that the base_path is "chrome.LATEST", and remove the extension. + // Ideally we would also check the value of base_path, but we cannot reliably + // log anything here, and aborting seems too harsh a choice. + new_path = new_path.ReplaceExtension(""); base::FilePath GenerateTimestampedName() is also used by StartLogRetrieval(), for debug_log_writer.cc... https://cs.chromium.org/chromium/src/chrome/browser/chromeos/system_logs/debug_log_writer.cc?type=cs&q=GenerateTimestampedName&sq=package:chromium&l=222 That's Chrome 62.0.3182.0~114
,
Mar 2 2018
Ah, it's fixed on ToT. Duplicated at bug 781363 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Oct 27 2017