New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 687025 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Buildbot page not opening when clicked on stdio link.

Project Member Reported by prashan...@samsung.com, Jan 31 2017

Issue description

The detailed pages for any of the steps as given below are not opening.

compile compile ( 17 mins, 41 secs )
-> stdio cache [stdout]

The error "This site can’t be reached" is seen.


 
Cc: simonhatch@chromium.org
The issue comes only for perf_bisect related builds.
Components: -Infra Infra>Platform>Buildbot
Can you please provide a link to an affected build?
I believe the preferred way to access those links is via the logdog urls now.
Unfortunately logdog links too do not work.

https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Fandroid_nexus6_perf_bisect%2F2951%2F%2B%2Frecipes%2Fsteps%2FFailure_reason%2F0%2Flogs%2Freason%2F0

This shows blank page with error in right top corner as

.../+/recipes/steps/Failure_reason/0/logs/reason/0	0 ... (Error)


I've logged in with my crendentials (prashant.n@samsung.com). Do I need to get any extra permission?

Components: -Infra>Platform>Buildbot Infra>Client>Perf
Owner: sullivan@chromium.org
Status: Assigned (was: Untriaged)
I don't think perf logs are publicly accessible. Assigning to sullivan for confirmation.
Status: WontFix (was: Assigned)
That's correct. We use release official builds for perf, and unfortunately they could contain information from partners that we don't have permission to share outside of Google.

Sign in to add a comment