Builds get stuck in "Cloning" state

[cajus]

Details

I wanted to migrate the project documetation to readthedocs, so I initially just added the github repository to RTD. It never leaves the "Cloning" state without any further information.

• Project: https://readthedocs.org/projects/qooxdoo-test
• Build #: lastest

[bonigarcia]

The same is happening to me in the following project:

https://readthedocs.org/projects/kurento/

... for the stable and latest build.

Please help

[SeanTAllen]

I am seeing the same thing

https://readthedocs.org/projects/ponyc

[Thesephi]

Confirming the same thing. Further information for reference:

• my project is hosted on a gitlab instance, and set to be publicly-accessible
• i can clone the project via http successfully (without any authentication)
• my repo contains only 1 file: README.md

[barbara-sfx]

Same here. My repo is private, if that makes a difference.

[severb]

Same here: https://readthedocs.org/projects/ringpop/builds/.

[barbara-sfx]

Making my private repo public fixed the problem for me. I am now waiting for a beta invite to readthedocs.com, which supports private docs.

[Phyks]

Same here https://readthedocs.org/projects/libbmc/build. My project is public.

[timofeymukha]

Experiencing kind of the same issue.
https://readthedocs.org/projects/eddylicious/

The repo is on bitbucket and is open.
However my project did work fine up to a point, and then the problems with cloning started.
Now, sometimes (like 1 out of 5) the docs would build. otherwise stuck in cloning.

As an example:

Cloning version latest (html)13 minutes ago
Cloning version latest (html)1 hour, 3 minutes ago
Cloning version latest (html)1 hour, 5 minutes ago
Passed version latest (html)3 hours, 32 minutes ago
Cloning version latest (html)3 hours, 33 minutes ago
Passed version latest (html)3 hours, 38 minutes ago
Cloning version latest (html)17 hours, 12 minutes ago
Cloning version latest (html)18 hours, 30 minutes ago
Passed version latest (html)1 day, 13 hours ago
Cloning version latest (html)1 day, 19 hours ago
Cloning version latest (html)1 day, 19 hours ago

[rthompsonj]

I too am encountering issues with a repo stuck in the "cloning" state. I have wiped my build. deleted, recreated, tried a new name, everything I can think of and it just sits at "cloning".

https://readthedocs.org/projects/caesar/builds/

Just for kicks I uploaded my project to github and the same issue is happening with the git version - I think this might be account related?

EDIT: turns out I had some bad formatting in my readthedocs.yml file, once I corrected that it was no longer stuck on the cloning phase. The previous ones stuck however, did not go away until I deleted and recreated the RTD project.

[agjohnson]

Okay, so a wide array of things going on here. The underlying issue is that we're not reporting build failures correct at exceptions during this phase, so I'll address that with this report.

If you are noticing this stuck behavior, there are a number of things that could be the cause:

• The repo you are trying to connect is private -- the community site will not support these repositories
• You typoed your repo URL
• There are network issues connecting to your repo -- rate limiting perhaps?
• We've noticed a spike in these issues when having memory issues on our build servers, the issue is intermittent

@severb ringpop seems to randomly fail on submodules, not sure why. Github rate limiting these requests perhaps? It might be best to track this separately.

[justincely]

I just hit this in one of my projects and my solution was similar to @rthompsonj. My issue was an incorrect path for the file attribute in readthedocs.yml. After fixing that, from a path that didn't exist, everything worked fine.

[prolic]

same here: https://readthedocs.org/projects/humusamqp/builds/4114297/

docs are public

[agjohnson]

@prolic your problem is you set your repository URL to a non-resolvable address https://prolic/HumusAmqp

[prolic]

Damn, my fault. Did not recognize this. Thanks!!!
Am 19.06.2016 03:24 schrieb "Anthony" [email protected]:

@prolic https://github.com/prolic your problem is you set your
repository URL to a non-resolvable address https://prolic/HumusAmqp

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#2047 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAYEvA9fjdrqMG8WljNsYpOrof8zi6stks5qNEXwgaJpZM4HqtTA
.

[Myoldmopar]

I seem to be having this problem as well now. Things worked great for so long, with one random cloning state a few months ago, but worked since then. I came back to work on the project and now it won't get past cloning. https://readthedocs.org/projects/common-pipe-redo/builds/

[benjaoming]

Same issue here. I have changed nothing in my setup, and now all branches seem to fail their builds. I have an oddly stuck process from 2 weeks ago, wondering if this where the issue comes from?

Project: https://readthedocs.org/projects/ka-lite/builds/

No readthedocs.yml file
Hosted on Github

[jagophile]

I am also having this problem. It was working fine and now I've had a build stuck in cloning for 5 days.

Project: https://readthedocs.org/projects/atomdb/
Github: https://github.com/AtomDB/pyatomdb

Any help appreciated.

[blaisep]

Hi @jagophile ,
I have this happen from time to time. The usual steps I take are:
* Does it build cleanly when I run Sphinx locally?
* When I run Sphinx locally are there any new warnings from the last working build?
* Do you get any console feedback when you click on the stuck entry in the Project->Builds listing? (Usually, this problem happens before that console is started)
* Next, try doing a Project->Versions->Wipe for the relevant version.

In a perfect world we would have better error reporting and exception handling during that crucial transition between the triggering of the build and the setup of the build vm.

[benjaoming]

@blaisep

My project builds fine locally, the problem is that nothing can happen because git clone fails:

Error
Failed to import project: Failed to get code from 'https://github.com/learningequality/ka-lite.git' (git clone): 1

Clicking Wipe doesn't help.

[jagophile]

THanks for the information. The step that "worked" for me was,
eventually, *Project->Versions->Wipe.
*The build now fails as I need to include a C module via ctypes. But that's
a different issue (and it seems a known one, that I am now trying to work
around)

I'm pretty sure I tried the wipe thing last week when this hung initially,
but maybe not?

Anyway, seems to be working-ish for now.

Adam

On 7 November 2016 at 12:47, Blaise Pabon [email protected] wrote:

Hi @jagophile https://github.com/jagophile ,
I have this happen from time to time. The usual steps I take are:

• Does it build cleanly when I run Sphinx locally?
• When I run Sphinx locally are there any new warnings from the last
  working build?
• Do you get any console feedback when you click on the stuck entry in the
  Project->Builds listing? (Usually, this problem happens before that
  console is started)
• Next, try doing a Project->Versions->Wipe for the relevant version.

In a perfect world we would have better error reporting and exception
handling during that crucial transition between the triggering of the build
and the setup of the build vm.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#2047 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGuMVVC0bVUGBVInvYC39whl1omghT_aks5q72QggaJpZM4HqtTA
.

[benjaoming]

@cajus - could you try changing your Git project path in Settings from https://githib.com/cajus/qooxdoo to https://githib.com/cajus/qooxdoo.git and building again?

[benjaoming]

Please note that as of PR #2497, better error messages have been displaying. For my case, it got solved and wasn't actually a problem in the RTD build, just the lack of feedback.

I would suggest to close this issue and instead focus on individual cases now that error messages are available instead of stuck in "Cloning" state.

[humitos]

I took a look at all of the project mentioned in this issues and most of them are:

• deleted (from github or RTD)
• wrong git url (using [email protected] into submodules)
• last builds are passing successfully

@agjohnson do you think there is something we need to do for this issue or we can close it?

If anyone from this issue has an update on the report I would appreciate. Thanks.

[benjaoming]

@humitos good summary.. see my comment above.. even if people have updates, it'd be better to open up new issues to reach a level of clarity that someone can work out a fix for (and nobody wants to do PRs that don't close issues).

[stanislaw55]

Hello,
currently I'm trying to setup local instance of RtD, using Docker to build docs (DOCKER_ENABLE = True in local_settings.py). However, no matter in which way I clone my repo, it still gets stuck in 'Cloning' state.

Updating git to version 2.15.1 doesn't change a thing.

Any help appreciated

[stanislaw55]

AFAICS, ReadTheDocs can clone my repo, and it does that, I can see it in user_builds. Next step is to create container and build docs inside it. That's the point where it enters 'Cloning' state. Here are mine four last output lines before 'Cloning'

[29/Dec/2017 09:03:50] readthedocs.doc_builder.environments:487[29310]: INFO Creating container
[29/Dec/2017 09:03:50] readthedocs.doc_builder.environments:487[29310]: INFO Creating container
[29/Dec/2017 09:03:50] readthedocs.core.views.hooks:58[29310]: INFO (Version build) Building dummy:latest
[29/Dec/2017 09:03:50] readthedocs.core.views.hooks:58[29310]: INFO (Version build) Building dummy:latest

[stanislaw55]

Nevermind, I've solved that problem. ReadTheDocs doesn't care about actual docker version. All you have to do is to set DOCKER_VERSION to 1.18 in local_settings.py

End... that's it. It works.

[humitos]

I'm closing this issue.

Feel free to create new issues (and link this one) in case there is something that it's not working as you expects.

For the stale states, a PR was merged that should mark them as failed: #3312

Thanks you all!