You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@broady was just doing a release, hit Ctrl-C with cmd/release, and then we noticed the two buildlets that got created didn't go away when his TCP connection did. They should:
user-release-darwin-amd64-10_10-0, created 1m56.050024014s ago, expires in 28m8.113784004s
user-release-linux-arm-0, created 1m55.677042811s ago, expires in 28m4.498193149s
The text was updated successfully, but these errors were encountered:
bradfitz
changed the title
x/build/cmd/coordinator: remote buildlets don't
x/build/cmd/coordinator: remote buildlets don't die on TCP disconnect
Dec 17, 2015
This bug was confused. cmd/release uses the same interface as gomote and gomote definitely doesn't need to keep a TCP connection open to keep a buildlet open. Nothing to fix here.
@broady was just doing a release, hit Ctrl-C with cmd/release, and then we noticed the two buildlets that got created didn't go away when his TCP connection did. They should:
user-release-darwin-amd64-10_10-0, created 1m56.050024014s ago, expires in 28m8.113784004s
user-release-linux-arm-0, created 1m55.677042811s ago, expires in 28m4.498193149s
The text was updated successfully, but these errors were encountered: