Cloning stuck for several hours

[ruslo]

Details

• Project URL: http://cgold.readthedocs.io/en/latest/
• Build URL (if applicable): https://readthedocs.org/projects/cgold/builds/4188199/
• Read the Docs username (if applicable): ruslo

Expected Result

Want to see cloning finished and move to the next step

Actual Result

"Cloning" stage stuck for several hours. Here is the link: https://readthedocs.org/projects/cgold/builds/ and screenshot in case it will disappear:

Interesting thing is that some commits after do successfully build but I see some missing parts of documentation. Another workaround solution for me is to cancel current build and run build again, but I don't see any "Cancel" buttons.

Thanks, Ruslo

[astrofrog]

I've been seeing this too

[humitos]

I'm marking this issue as Needed: more information since it seems to be only one isolated case between a lot of successful builds and there is nothing publicly available to take a look.

@agjohnson I think we will need to jump into the servers log or something like that.

[ericholscher]

This is a bug that we have, when a process gets killed uncleanly, the build state never gets re-updated. It is a known issue, so I'm going to close this specific issue, and hopefully we'll fix it soon.

[ruslo]

It is a known issue

@ericholscher This one #2471?

[ppwwyyxx]

Seeing this issue on this build: https://readthedocs.org/projects/tensorpack/builds/5221274/ right now.

[ericholscher]

This is caused by the builds being killed, likely by a bug on our side. We need to write some cleanup code, but don't worry, it isn't still running on our infra, we just aren't updating the DB state correctly. If you trigger another build it will likely work, if not that's a larger issue.

…

On Thu, Mar 30, 2017 at 12:32 AM, Yuxin Wu ***@***.***> wrote: Seeing this issue on this build: https://readthedocs.org/ projects/tensorpack/builds/5221274/ right now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2295 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABjpkTcRwQDsEgrZZnV0jsyI9dDdm-Pks5rq1qZgaJpZM4JKcx3> .

-- Eric Holscher Maker of the internet residing in Portland, Oregon http://ericholscher.com

[mennamorato]

Just ran into this exact issue see: https://readthedocs.org/projects/aviatrix/builds/5570271/
Triggered a new build that passed. So this "cloning" forever is just an artifact, not a real process is what above comment seems to say?