Skip to content

Build passed but no documentation or downloads #3159

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

Closed
mcraig-ibme opened this issue Oct 12, 2017 · 10 comments
Closed

Build passed but no documentation or downloads #3159

mcraig-ibme opened this issue Oct 12, 2017 · 10 comments
Labels
Bug A bug

Comments

@mcraig-ibme
Copy link

Details

Expected Result

Documentation and downloads available after build passed

Actual Result

There's no indication of a problem in the build, but no documents are visible. I tried recreating the project under a different name. I have another similar project which is working fine. The only difference I can find between them is that in the working project the 'Overview' page displays 'latest' in the 'Versions' box whereas in the non-working project this box is empty. However the 'latest' version is listed in the 'Versions' page and is active. I've also tried 'wiping' the 'latest' version.

@RichardLitt
Copy link
Member

Related to #2356.

@RichardLitt RichardLitt added the Bug A bug label Oct 12, 2017
@mcraig-ibme
Copy link
Author

Worth mentioning that the docs on my working project are updating when I rebuild so it's something specific to my new projects - it looked to me like #2356 was to do with queuing of updates which would presumably affect all projects?

@ShawnDriscoll
Copy link

ShawnDriscoll commented Oct 13, 2017

I don't think any PDFs or EPUBs have been generated for any projects since Oct. 9th. Servers need looking at for broken chain. I have not looked to see if HTML is being generated for downloads.

ADDED:
Looks like HTML docs are not being generated either after receiving new files from GitHub.

@pietmolenaar
Copy link

pietmolenaar commented Oct 16, 2017

I'm seeing the same here in four RTD projects, no PDF's or EPUBs generated since Oct. 9th; Output in log is identical to the latest versions that did build, latex says a pdf was generated, but probably not copied to the right location?
Added: two of the project urls:
https://readthedocs.org/projects/r2-tutorials/
http://manual.cytoscape.org/en/latest/

@sasha-carlos
Copy link

The same behaviour with downloads in http://findface.readthedocs.io/en/latest/.

@mcraig-ibme
Copy link
Author

My existing projects are still working fine but not new ones. If it helps, I have noticed the 'latest' version is missing from the overview version list in the non-working projects:

image

Also, in 'Admin->Versions', the 'latest' version is listed as 'Not built':

image

However it's been built several times:

image

Could there be some problem with identifying the version to publish?

@bloer
Copy link

bloer commented Oct 19, 2017

Same problem in http://bgexplorer.readthedocs.io/en/latest/ . New project started today, build passed, but nothing in Downloads and homepage shows autogenerated index file.

@mcraig-ibme
Copy link
Author

Here's something weird: I can only build and download these documents when I'm not logged in to RTD!
Of course they don't deploy to the web but you can download HTML/PDF etc.
But if I'm logged in, no downloads are listed.
Not sure if this might be relevant to the problem.

@vegu
Copy link

vegu commented Nov 23, 2017

So i ran into the same problem as @mcraig-ibme, with the exact same symptoms, in my case it appears to have been a missing index.md

Adding that file and making sure it exists in mkdocs.yml fixed the issue for me

pages:
  - Home: index.md

Odd that it's not more vocal about this. Anyway, maybe it's the same issue on your end?

@mcraig-ibme
Copy link
Author

mcraig-ibme commented Nov 24, 2017

I think it was! I'm using the conf.py method and RST but my main index file was not named index.rst. So I renamed it to index.rst and changed the master doc in conf.py to:

master_doc = 'index'

Now everything is working and all the symptoms I described above have gone away.

However my old master doc was specified correctly in conf.py so I would have expected it to work. Not clear if this is a bug or not, but it's clearly a nasty gotcha.

Many thanks @vegu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug
Projects
None yet
Development

No branches or pull requests

7 participants