Is this available to you: https://luci-milo.appspot.com/buildbot/tryserver.chromium.perf/android_nexus6_perf_bisect/2868 ?

That link, yes, but not the individual outputs.

For instance, I don't have access to:

http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2868/steps/Performance%20Test%20%28With%20Patch%29%201%20of%201/logs/Captured%20Output

Try this: https://luci-milo.appspot.com/buildbot/tryserver.chromium.perf/android_nexus6_perf_bisect/2991

and click on "(logdog)"

If you have access to that, it means that the build you are looking at happened before we enabled cloud logging (logdog), and since there have been a number of builds beyond the one you're looking for, the logs cycled and it's no longer available.

I tried a https://codereview.chromium.org/2704133004/ which was done last night.

All [logdoc] links give me:

"./+/recipes/steps/recipe_result/0/logs/result/0	0 ... (Error)"

All other links give me:

"This site can’t be reached. Connection was reset"

Dan - can you help?

I don't think so. The logging is configured to log to the "chrome" pool, which is an internal pool with only Googler access. Relaxing that to allow non-Googlers without exposing all internal logs to non-Googlers would require:

1) Create a new luci-config project for perf (config change).
2) Start logging new logs to that project (config change).

This will, unfortunately, not apply retroactively, so existing logs will not become available. If they *must* be made available, it will require engineering effort to implement a whitelist.

Regardless, I am not an authority on determining how these logs should be exposed to non-Googlers, either in part or in full, so I can't really do anything here. +sullivan@, can you weigh in here?

My understanding is that we need to restrict the logs to prevent possibly leaking data from partners, since these are release official builds.

Is it the results.html file you need, or do you need the actual logs?