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

Many builds stuck in "triggered" state #435

Closed
gatesphere opened this Issue Aug 12, 2013 · 13 comments

Comments

Projects
None yet
6 participants
@gatesphere
Copy link

gatesphere commented Aug 12, 2013

I have a script that runs for the leo-editor project requesting a nightly build. Every build since July 24th has been stuck in the "Triggered" state. Is there any way to cancel/delete these builds? I have disabled the nightly script that triggers these builds until I can find a solution to this problem.

@mitechie

This comment has been minimized.

Copy link

mitechie commented Aug 20, 2013

I've got this with a fresh project I setup 'charmworld'. Each build is stuck in triggered state for the last 3 days. Since it's in 'triggered' there's no failure message, logging, or other utility I can see to debug the issue.

@ericholscher

This comment has been minimized.

Copy link
Member

ericholscher commented Aug 20, 2013

It's almost certainly our bazaar support being broken. Nobody on the core team, and very few of our users use bzr, so it's support is half-baked at best.

@ericholscher

This comment has been minimized.

Copy link
Member

ericholscher commented Aug 20, 2013

Likely #349

@gatesphere

This comment has been minimized.

Copy link
Author

gatesphere commented Aug 26, 2013

:-/

@gatesphere

This comment has been minimized.

Copy link
Author

gatesphere commented Aug 29, 2013

Our team "fixed" this by setting up a nightly git mirror here on github. It pulls from bzr and pushes to git nightly, and then fires off the curl POST to request another build.

That said, we have 2 weeks of docs still stuck in "Triggered" state.

@cjwatson

This comment has been minimized.

Copy link

cjwatson commented Sep 25, 2013

@gatesphere: Is it better now? I fixed #349 and my project is working again.

@gatesphere

This comment has been minimized.

Copy link
Author

gatesphere commented Sep 25, 2013

Still have several builds in "Triggered" state, but that doesn't matter. The recent builds have been working successfully, but they're reading from our nightly git mirror. I'm unlikely to try with bzr again, as the git mirror serves a dual purpose anyway.

Thanks for checking in, though.

@ericholscher

This comment has been minimized.

Copy link
Member

ericholscher commented Sep 27, 2013

Closing this for now. Thanks @cjwatson!

@youngsterxyf

This comment has been minimized.

Copy link

youngsterxyf commented Nov 14, 2013

@ericholscher my project is also stucked in “triggered” state
qq20131114112343

@youngsterxyf

This comment has been minimized.

Copy link

youngsterxyf commented Nov 14, 2013

@ericholscher The source code of this project is hosted on github,and i add “readthedocs” hook for this project。This project is here,Thank you!

@codedstructure

This comment has been minimized.

Copy link
Contributor

codedstructure commented Nov 19, 2013

I had exactly the same issue with a (Mercurial) project (pylibftdi) hosted on bitbucket, and 'resolved' it in the same way by pointing to a github mirror - so it seems it isn't just bzr which is having / had issues.

@cjwatson

This comment has been minimized.

Copy link

cjwatson commented Nov 19, 2013

Perhaps there should be separate issues for the git and Mercurial problems, since the bzr problems were definitely traceable to a bug specifically in rtfd's bzr code.

Any bug that causes the import of a project to crash will result in this symptom, so separate instances of it should really be separate issues in the same way that different crashes in any project should be separate bugs.

@codedstructure

This comment has been minimized.

Copy link
Contributor

codedstructure commented Nov 19, 2013

Thanks, opened new issue as #547

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.