Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/build: dragonfly getting stuck on builds #27405

timdarbydotnet opened this issue Aug 31, 2018 · 1 comment

x/build: dragonfly getting stuck on builds #27405

timdarbydotnet opened this issue Aug 31, 2018 · 1 comment


Copy link

@timdarbydotnet timdarbydotnet commented Aug 31, 2018

The revert commit a700ae9 fixed a problem that was causing the dragonfly builder to hang forever (instead of failing) when attempting to build anything later than commit e6c1594. Please manually fail commits:

Otherwise, the builder will continue to revisit those commits and hang.

@gopherbot gopherbot added this to the Unreleased milestone Aug 31, 2018
@gopherbot gopherbot added the Builders label Aug 31, 2018
@dmitshur dmitshur self-assigned this Sep 4, 2018
Copy link

@dmitshur dmitshur commented Sep 5, 2018

Ok, I've learned how to do this and manually failed those builds now. It should be safe to keep the dragonfly builder running now. Please let me know if there's anything else.

For posterity, I used the approach @bradfitz recommended, which was to hit the /result endpoint of the dashboard ( manually with a one-off Go command; I'll clean it up and upstream it if this needs to be done more often. It was based on this code in cmd/coordinator. That endpoint requires a builder key, which I have access to.

Ideally, we should resolve the underlying issue and make it so that the builder has a timeout and doesn't hang forever on some bad commits.

@dmitshur dmitshur closed this Sep 5, 2018
@golang golang locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants