Build #4342378 stuck in Building state

[mitya57]

Details

• Project URL: https://readthedocs.org/projects/secretstorage/
• Build URL (if applicable): https://readthedocs.org/projects/secretstorage/builds/4342378/
• Read the Docs username (if applicable): mitya57

Expected Result

The build either completes, or fails, or times out.

Actual Result

The build is stuck in Building state for more than a month. All other builds went fine.

[afabiani]

Have a similar issue here

https://readthedocs.org/projects/geonode/builds/4537979/

the "latest" branch works while the "master" one stucks on "cat conf.py"

[conor10]

All of my builds are stuck on "cat conf.py", doesn't make a difference for me whether I build latest or master, see #2476

[markcmiller86]

I am running into this constantly. My doc tree builds fine running Sphynx directly on another linux platform and I get literally no feedback what is going on in RTD. I am finding it very unusuable.

[conor10]

Yes it's a shame, it's great when it's working. I'm manually building & deploying my docs to GitHub Pages to work around the issue. RTD was always getting stuck at exactly the same point in my build.

cat conf.py

Although looks as though my build history console output is now missing too, so I can no longer see what causing the build failures :(

[gtalarico]

Same issues.
Worked fine every time, then after last build it keeps getting stuck on
cat conf.py

/revitpythonwrapper
Build #4641434
latest (adf3db113c0feaddc4fa2279d36fe090f8d5dbba)

[gtalarico]

following up made a trivial change to project settings, and it got rebuilt successfully.
previous build still stuck:

[conor10]

I've tried modifying all sorts of different build settings, still hasn't made a difference for me unfortunately.

[fulopattila122]

@gtalarico and what was that magic trivial change? :)

[humitos]

@mitya57 one of the problem I see here is your conf.py makes the server goes into a:

RecursionError: maximum recursion depth exceeded

because you are returning the same Mock() class instead of MagicMock() at this line: https://github.com/mitya57/secretstorage/blob/master/docs/conf.py#L79

After changing that in my local clone of your repository, I was able to build it without any problem.

Can other people having this issue confirm that you are not running into the same problem?

[mitya57]

@humitos

because you are returning the same Mock() class instead of MagicMock()

Oh, that was because that was documented in the FAQ before #2530 was merged. I have updated it now. If you kill the outstanding running build, I think we can mark the issue resolved.

[humitos]

@mitya57 there is no way to kill a building (see #2471) but that is not a problem for this since it's just a UX issue. I mean, the building process doesn't exist anymore in the server, there is nothing running but the thing is it is not communicated properly to the Front End (#2407)

Thank you. I'm closing this issue.

Feel free to re-open if any of you still have the problem.