-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Comments
It seems like I'm running into the same problem, see https://readthedocs.org/projects/easybuild/builds/7076258/ |
@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). |
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. |
@stsewd is the project that you tried ipyleaflet? |
I started another build (https://readthedocs.org/projects/ipyleaflet/builds/7076823/), and I am getting
|
Starting it again (https://readthedocs.org/projects/ipyleaflet/builds/7076842/) gives no log at all. |
@SylvainCorlay yes, I tried
That's because the command is still running, on my local installation, I can see that this command is See #3613 |
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. |
@SylvainCorlay I can see that the failure is because of a bad configuration file |
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 |
I have this issue on most of the packages that I maintain at the moment (over 20), and it is a new issue. |
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
|
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 |
Details
Expected Result
I expect to see logs for the failed builds
Actual Result
The content of the page is "latest (6938f2dbe0edc0b26c949b6d14bedead40d47772)".
The text was updated successfully, but these errors were encountered: