Data missing when viewing logs in LogDog |
||||||
Issue descriptionGo to: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf.fyi%2FAndroid_Swarming_N5X_Tester%2F385%2F%2B%2Frecipes%2Fsteps%2Floading.mobile_Dashboard_Upload%2F0%2Flogs%2Fjson.output%2F0 and look for "143.79000000096858" and go to the third entry. Below that is the entry: "https://www.google.co.id/#q=pengiriman+bunga": { "description": "time to first contentful paint", "important": false, "improvement_direction": "down", "name": "timeToFirstContentfulPaint_max", "page_id": 8, "std": 37.801221414650854, "type": "list_of_scalar_values", "units": "ms", ] }, It is missing the entry for "values" (see entry above in page for example). Since the uploading of data to the dashboard is not complaining, it is reasonable to believe at that point the data is intact. (adding Annie who can either confirm this suspicion or add someone who can). Martiniss@ looked at the log and determined this occurred at the edge of two log-entry-chunks.
,
Mar 3 2017
It looks like this is a bug in the LogDog viewer. When I dump via CLI, I get:
"https://www.google.co.id/#q=pengiriman+bunga": {
"description": "time to first contentful paint",
"important": false,
"improvement_direction": "down",
"name": "timeToFirstContentfulPaint_max",
"page_id": 8,
"std": 37.801221414650854,
"type": "list_of_scalar_values",
"units": "ms",
"values": [
215.04199999943376,
161.58300000056624
]
},
That's good news, since it means the data isn't missing, just not rendering properly.
,
Jul 11 2017
Dan, do you think it's still worth investigating or just archive?
,
Jul 11 2017
This still needs to be fixed. I'd keep it Untriaged for now. Need to make time to close some viewer bugs in the near future, I'll try and roll this in.
,
Jul 11 2017
Sounds good, but please use available for this, when a team member has looked over the bug it's been triaged.
,
Jul 12
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. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 18
,
Sep 26
We have a new viewer now, so maybe this is fixed (unfortuantely this specific log was lost due to a separate bug). |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by martiniss@chromium.org
, Mar 3 2017