New issue
Advanced search Search tips

Issue 687337 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Trouble getting a trace file for a graph on the performance dashboard

Project Member Reported by erikc...@chromium.org, Jan 31 2017

Issue description

https://chromeperf.appspot.com/report?sid=e85cfd4e3214f04d31480911cd91c6723d717b9c45215fdfaaca25e581c04413

There's a large jump around 445739. I wanted to see the trace. 

1) I click on the relevant data point, and then click "trace". This brings up a dialog about recording a new trace. That's not what I want.

2) I clicked on "buildbot stdio". This repeatedly brings me to a page with no content. I try signing in, no change.

3) After trying (2) several times, I eventually got the page to load [I haven't been able to reproduce this...]. This points me to https://chromium-swarm.appspot.com/user/task/33ea40b2197c9810. This has the log:
"""
INFO:py_utils.cloud_storage:Uploading /b/s/w/itIOURAy/tmpXd_MCA.html to gs://chrome-telemetry-output/trace-file-id_0-2017-01-24_12-04-27-49580.html
View generated trace files online at https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_0-2017-01-24_12-04-27-49580.html for page about:blank
"""

4) Navigating to that link gives:
"""
Forbidden

Error 403
"""

5) Downloading the gs file directly and opening it, I don't see any memory-infra nodes.



 
Screen Shot 2017-01-31 at 2.21.00 PM.png
171 KB View Download
Screen Shot 2017-01-31 at 2.21.05 PM.png
74.4 KB View Download
Screen Shot 2017-01-31 at 2.21.51 PM.png
266 KB View Download
The log in https://chromium-swarm.appspot.com/task?id=33ea40b2197c9810&refresh=10&show_raw=1 belongs to system_health.common_desktop desktop, not the memory one. So that's why you don't see memory-infra data.
Status: WontFix (was: Untriaged)
Okay - I didn't have the right "subtest" selected - I've attached a screenshot with then necessary configuration.

This still 403s, but opening with @google credentials fixes that problem.
Screen Shot 2017-01-31 at 2.50.48 PM.png
81.9 KB View Download

Sign in to add a comment