The URL that "Leads to" points to is actually a BuildBot URL. If that's not loading, it's b/c BuildBot is timing out.

No, I think it's because this waterfall is now LogDog only. IIUC, that link isn't even supposed to be there.

The waterfall is LogDog-only, and the link (when it loads) is useless:

https://screenshot.googleplex.com/4CaYGa0Mfyp.png

However, it is supposed to load, and the failure that you're getting is because of BuildBot timing out. LogDog log URLs are: "https://luci-logdog.appspot.com/...".

I think I'm going to mark this "WontFix", since I suspect you were just hitting BuildBot unavailability, not an actual LogDog issue. Please re-open if I'm incorrect here.

> However, it is supposed to load, and the failure that you're getting is because of BuildBot timing out. LogDog log URLs are: "https://luci-logdog.appspot.com/...".

I'm not following. This is a link to a non-LogDog URL from the buildbot page. I think the issue is that the link isn't even supposed to be there?


It's not timing out for me, I get connection reset immediately. I've had the same experience for several days, and I get it every time, so it's not flaky.

From your screen shot I can't see which URL you navigated to. Is that from https://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect_builder/builds/14589/steps/compile%20%28with%20patch%29/logs/stdio ?

The link is currently supposed to be there. It's useless, but it's supposed to be there, because we haven't implemented a way to change the BuildBot template to not show it effectively. This is actually something that's come up recently, and I am intending to work on, but ATM this is WAI.

Yes, that is the URL that I went to. Note that it starts with "build.chromium.org". It is not a LogDog URL, so it timing out is not a problem with LogDog.

I've tried that URL a hundred times and get "connection reset" each time, so I'm not sure why you can get to it and not me.

I'm not saying that URL being broken is a LogDog problem.

But having "stdout" link to a page that results in "connection reset" (or is otherwise useles as you say) seems like a problem with the LogDog conversion, so it probably should be tracked somewhere.

There are two issues here:

1. tryserver.chromium.perf buildbot URLs dont' work on build.chromium.org/p/ because they are internal.  they only work on uberchromegw.corp.google.com/i/.  In fact tryserver.chromium.perf is a misnomer, it should really be tryserver.chrome.perf :/

2. It's not clear that even in logdog only mode, the "stdio" link still links to buildbot.  https://chromium-review.googlesource.com/450019 should fix that.

I'm seeing two things here:
1) BuildBot shouldn't have useless links. Agreed. As I mentioned in #6, this is something being actively worked on. In the meantime, the link is valid (albeit useless) and should function, except...

2) BuildBot shouldn't have links that time out. I don't know what to say here. It doesn't time out for me, but BuildBot is notoriously easy to overwhelm and susceptible to things being flaky and timing out. This is a known problem that isn't getting any better, and is a large part of the motivation for developing an extra-BuildBot logging system in the first place. This can't and won't be fixed.

The link having "connection reset" has absolutely nothing to do with LogDog or the LogDog-only conversion.

Following up on #9, if this build weren't LogDog only, the link in question would have the full build log, and I would expect it to also time out for exactly the same reason that it's timing out right now.

RE the timeout: please file a trooper ticket and have the current on-call trooper look into why BuildBot isn't serving you data.

It's not a timeout; the server resets the connection immediately after receiving the request.

$ curl  'https://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect_builder/builds/14589/steps/compile%20%28with%20patch%29/logs/stdio' > /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (56) SSL read: error:00000000:lib(0):func(0):reason(0), errno 104


Before the LogDog conversion, that link worked fine.

I'm not going to bother you with this anymore, I'll try to remember not to click those links.

hinoka@ just pointed out to me that is a perf waterfall. Perf logs are special, and are intentionally are not accessible through any method other than LogDog. Those links being there will never work from an unauthenticated endpoint such as "build.chromium.org".

But even if they did work, they are useless logs (as I linked above in that screenshot) that are an implementation detail of BuildBot now. We're actively working to remove those links from the build so they aren't confusing. This should be implemented pretty soon.