Skip to content

Build logs unavailable #3993

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
SylvainCorlay opened this issue Apr 21, 2018 · 14 comments
Closed

Build logs unavailable #3993

SylvainCorlay opened this issue Apr 21, 2018 · 14 comments
Labels
Support Support question

Comments

@SylvainCorlay
Copy link

Details

Expected Result

I expect to see logs for the failed builds

Actual Result

The content of the page is "latest (6938f2dbe0edc0b26c949b6d14bedead40d47772)".

@boegel
Copy link

boegel commented Apr 21, 2018

It seems like I'm running into the same problem, see https://readthedocs.org/projects/easybuild/builds/7076258/

@stsewd stsewd added the Support Support question label Apr 21, 2018
@stsewd
Copy link
Member

stsewd commented Apr 21, 2018

@SylvainCorlay did you try building locally? How long (and much memory) does it take? I tried on my local instance and I had to increase the memory and time limit to build successfully (build took 1267 seconds).

@SylvainCorlay
Copy link
Author

Yes, the docs build fine locally. The HTML build takes about half a second on my 6 years old macbook, and python takes up 46MB of memory during that time.

@SylvainCorlay
Copy link
Author

@stsewd is the project that you tried ipyleaflet?

@SylvainCorlay
Copy link
Author

I started another build (https://readthedocs.org/projects/ipyleaflet/builds/7076823/), and I am getting

Error
There was a problem with Read the Docs while building your documentation. Please report this to us with your build id (7076823).

@SylvainCorlay
Copy link
Author

SylvainCorlay commented Apr 21, 2018

Starting it again (https://readthedocs.org/projects/ipyleaflet/builds/7076842/) gives no log at all.

@stsewd
Copy link
Member

stsewd commented Apr 21, 2018

@SylvainCorlay yes, I tried ipyleaflet.

Starting it again yields no log at all

That's because the command is still running, on my local installation, I can see that this command is conda env create ... which gets killed due to excessive memory consumption, so I suspect the same is happening on rtd.

See #3613

@SylvainCorlay
Copy link
Author

I am seeing the same kind of issue (no build log) with a new project: xhale

https://readthedocs.org/projects/xhale/

The build takes one second to fail and there is no information whatsoever.

screen shot 2018-04-22 at 11 32 50 pm

@stsewd
Copy link
Member

stsewd commented Apr 22, 2018

@SylvainCorlay I can see that the failure is because of a bad configuration file

screenshot-2018-4-22 xhale read the docs

@SylvainCorlay
Copy link
Author

Thanks, this log appeared more than 20 hours after the build appeared as failing..

The new issue is that we don't see any log for most repositories when the build fails.

It started late last week, on multiple organizations and repositories: See e.g. the build for pythreejs: https://readthedocs.org/projects/pythreejs/builds/7083409/

screen shot 2018-04-23 at 2 14 58 pm

@SylvainCorlay
Copy link
Author

SylvainCorlay commented Apr 23, 2018

I have this issue on most of the packages that I maintain at the moment (over 20), and it is a new issue.

@agjohnson
Copy link
Contributor

You need to refresh without cache, your browser is using an out of date JS asset. We should invalidate these assets somehow, but that's another issue.

@SylvainCorlay
Copy link
Author

SylvainCorlay commented Apr 23, 2018

You need to refresh without cache, your browser is using an out of date JS asset. We should invalidate these assets somehow, but that's another issue.

Thanks! This fixed the issue! I can see the logs now.

Although I am getting the infamous

Error
There was a problem with Read the Docs while building your documentation. Please report this to us with your build id (7083414).

https://readthedocs.org/projects/pythreejs/builds/7083414/

@agjohnson
Copy link
Contributor

Oops yeah, that's a new problem with docker from a deploy last week. I'll close the issue here as we're addressed the docker change in #3999

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

No branches or pull requests

4 participants