prow issues about test-infra

[ldemailly]

somehow I can't assign so cc @nlandolfi and @sebastienvas

[ldemailly]

also seems more flacky - I got 2x failure only prow

[ldemailly]

for instance: istio/istio#470 (comment)

[sebastienvas]

Prow currently only run on master. I don t hink Prow is actually more flaky as Prow and the e2e testing cluster are in the same zone. The only difference that I can spot is that Jenkins is using 1.6.0 while Prow is using 1.6.4.

[nlandolfi]

I think we have resolved these over the past few weeks and also through clarifications in conversation but let me know if not!

1. We pointed out that prow.istio.io has the logs when the job is running. We are working on having the Github status link go directly to these live logs while the job is running, and then link to the durable storage logs (Gubernator) once the build has completed. This relies on a slight change to the upstream Prow project.

2. Yes I believe it is user-agent magic. I think we talked about how ctl-f works, and you can curl if you want the text. We also made the bucket public to GCS web ui, for browsing.

3. Yes, that was skipped because we were only running presubmits to master. This makes sense from a resource conservation point of view, but perhaps not from the development point of view. Which branches we run jobs for is specified in the prow configuration "branches" block. I enabled it on all branches for istio/istio with this PR.

4. Those links are now working. let me know if still having issues.