-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
web3j build is stuck & subsequent builds all fail due to a file lock issue #2476
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
Subsequent builds are now not working either, so I can't update the web3j docs :-( Build #4576621 [Errno 30] Read-only file system: '/home/docs/checkouts/readthedocs.org/user_builds/web3j/latest__rtdlock' |
Details
Expected ResultBuild should complete. Actual ResultI believe I see the same issue. Attempted to build two times and each time the build fails just after start. The following error is reported:
|
The issue with builds on my repository have been resolved with #2475 (comment) |
Thanks for letting me know @krzychb. Unfortunately my builds are still hanging at the below point every time. |
I've tried deleting & recreating my project, but still encounter the same issues unfortunately. |
Hi @conor10, I am sorry to hear that. I have a new case when my build started off, step by step very slowly, to finally get stuck like below. It is still like that. I do not see the clue in the log why is it so. Then, after an hour or so, I have started another build and this one passed in 123 seconds I am using Read the Docs just for coupe of weeks now and do not have much experience. In this case, as you already did "deleting & recreating your project", I would check the Barebones example of a ReadTheDocs repo. This is to rule out your current repository as potential source of issues, I have started with this particular example and it worked for me from the first try. Krzysztof |
@conor10 it seems your last build is passing. What did you change? Is your issue solved? Let me know if we can close this one. |
Looks like this is working now (I missed the above message and haven't checked RTD in months as I was updating docs manually instead). I didn't ever change anything on my side. It magically started working again. |
Details
Expected Result
Build should complete.
Actual Result
Build has been stuck for over 2 hours
The text was updated successfully, but these errors were encountered: