logdog: Some streams failed to load. |
|||
Issue descriptionI was doing archaeology for a perf bug and was blocked by logdog failing to show me this log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5X_Perf__1_%2F3794%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_mobile%2F0%2Flogs%2Fjson.output%2F0# It says: Some streams failed to load. Devtools says: elements.html:15514 Error loading buffer for chrome/bb/chromium.perf/Android_Nexus5X_Perf__1_/3794/+/recipes/steps/system_health.memory_mobile/0/logs/json.output/0 ( _BufferedStream ): Error: could not parse response(…) I never had this problem with gsutil.
,
Dec 5 2016
LogDog is significantly different from gsutil. In many ways it's better, and in some other ways it's worse on virtue of complexity. This particular issue was a bug with the log viewer, which is not very good on account of both time and the fact that it's the first large HTML/JS app I've written. That said, I've pushed a new viewer app rewrite to production this morning and the issue is no longer present, so try again :)
,
Dec 11 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 2 2018
Looks like Dan fixed this a year ago. |
|||
►
Sign in to add a comment |
|||
Comment 1 by estaab@chromium.org
, Dec 1 2016