-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Builds for the past three days seem to fail #2984
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
Comments
Your build says it completed successfully yet it didn't. So this is the exact opposite of #2982. |
@marcelstoer - I'm not quite following. I don't see any failed builds here: https://readthedocs.org/projects/go-ontology/builds/ |
@cmungall I may be the source of confusion: the builds have the label saying they are "passing", but something must be broke and thus I wrote in the issue that builds 'seem to fail', for lack of better description. Even if builds are 'passing', the documentation display is still wrong. And I'm out of options to update from the Admin panel. I'm also a little surprised that it has been 6 days and we have not heard back from RTD friends; I am hoping it's because #2981 is probably still taking most of their attention. |
Unfortunately it's been another 3 weeks, and http://go-ontology.readthedocs.io/ is still not building as expected |
I burned http://go-ontology.readthedocs.io/ and created http://ontologydocs.readthedocs.io/en/latest/ instead. Error persists and it is not building as expected. Also getting the sense that I am sending messages to the void here? :( |
http://ontologydocs.readthedocs.io/en/latest/ makes a request to which fails with HTTP 404. I guess that's why loading the rest of the page i.e. all CSS artifacts is then aborted and you get the "unstylish" look. @agjohnson is that an obvious problem you've seen before? |
not sure if this helps, but it looks like there is a giant blank spot in the head section of the HTML
|
Oh, that'd be a more logical explanation why CSS artifacts are not loaded 🙁 |
Thanks for your help @marcelstoer and @cmungall. I changed the theme from 'default' to 'alabaster' in my configuration, and that blank space at the top went away.
Improvements to styling on the documentation pages are visible at The reason behind that 404 with the default theme may remain a mystery. |
@monicacecilia Hi, I can see that your docs look good now, are you still having this issue? |
@stsewd yep. it seems to be working now. this can be closed. cheers. |
@monicacecilia thanks for the update! |
Details
Project URL:
http://go-ontology.readthedocs.io/
Build URL (if applicable):
Latest build today: https://readthedocs.org/projects/go-ontology/builds/5627360/
Also at: http://go-ontology.readthedocs.io/en/latest/
Read the Docs username (if applicable):
monicacecilia
Expected Result
I hoped to see the usual display for all documentation. That is, the web page with black / blue / white backgrounds, browsable content with index table on the left, etc. For an example, see this other project of ours (screenshot):
Actual Result
Instead, all I I see is an old-timey HTML page (without formatting) and with broken links for a number of files, for example these URLs:
http://go-ontology.readthedocs.io/en/latest/DailyWorkflow.html#commit
http://go-ontology.readthedocs.io/en/latest/Configs.html
Examples:

The text was updated successfully, but these errors were encountered: