New issue
Advanced search Search tips

Issue 735594 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Logdog errors in a build

Project Member Reported by martiniss@chromium.org, Jun 21 2017

Issue description

https://build.chromium.org/p/chromium.perf/builders/Win%20Builder/builds/86175 is the relevant build. https://build.chromium.org/p/chromium.perf/builders/Win%20Builder/builds/86175/steps/steps/logs/stdio shows the logdog messages. There's a bunch of this at the end:

[W2017-06-21T11:10:48.292992-07:00 3676 0 pubsubOutput.go:220] TRANSIENT error publishing messages; retrying... {"error":"rpc error: code = 13 desc = connection error: desc = \"transport: read tcp 192.168.110.237:56219->172.217.12.106:443: wsarecv: An existing connection was forcibly closed by the remote host.\"", "count":1, "delay":"500ms", "pubsub":"pubsub(projects/luci-logdog/topics/logs)"}


Not sure if logdog could do anything about this, but it seems bad that logdog has been stuck here for about an hour.
 

Comment 1 by d...@chromium.org, Jun 21 2017

I haven't seen that one before. Looks similar to:
https://github.com/grpc/grpc-go/issues/1062
https://groups.google.com/forum/#!topic/golang-nuts/3-91XzbcCg0

This might already be fixed; we haven't rolled Butler in a while. Other than killing the build, I don't really know what can be done.
Components: Infra>Client>ChromeOS Build
Status: Archived (was: Untriaged)

Sign in to add a comment