-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Error: An unexpected error occurred #2985
Comments
Hitting this issue as well, but I just checked my latest public build and the updated docs are actually showing up correctly. So even though it is telling me I have a failed build (with the "unexpected error occurred" message), the docs are actually building and showing up. |
Dup of #2982 |
Get the same on my project. |
I have the same problem; builds are reporting as failed, but the updated docs are being installed. It seems something fails after the 'Installing' step. Example build URL: https://readthedocs.org/projects/uhack-guide/builds/5635512/ |
I have been facing this issue since the past week(( so the documentation on my project can not be updated... UPD: Today it works ok for my project! Thanks! UPD2: Now it works ok! Thanks again! |
Same here. Builds are showing new HTML but reporting as failed: Example Build URL: https://readthedocs.org/projects/drush/builds/5646326/ |
I tried creating a new project (from the same source repo in Bitbucket), to no avail - builds still report 'unexpected error' but the HTML is built successfully. Eg: https://readthedocs.org/projects/uhack-guide-2017/builds/ |
Mine project failed and the HTML document is not created. http://yaj.readthedocs.io/en/latest/ |
I believe this is a problem with unicode that was introduced with either changes for py2/3 compatibility or recent changes to our file syncing code. |
Yup, underlying it is an issue with YAML and unicode. Fix at #2998 |
Build still failing:
|
I also have this problem. Build: https://readthedocs.org/projects/dissonance/builds/5688334/ As others have said, the build reports a failure but the live version of the docs appears to be up to date. |
https://readthedocs.org/projects/link-blockchain/builds/5713802/
|
The issue seems to be resolved. My project started building successfully a day ago (7/20/2017) and it seems many of the projects here are building successfully as well now. |
same problem here, it only says "An unexpected error occurred", don't know what to do: |
Same problem: "An unexpected error occurred" |
Also seeing this one https://readthedocs.org/projects/stack/builds/5876544/. It would be much nicer to see a stack trace here instead of 'unexpected error'. |
Coming back to this, I see that we're both (the OP and I) complaining about this bad error message. Maybe I should just do something about fixing this myself instead of moaning :) Can any core dev seeing this perhaps point me in the right direction and I'd definitely take a stab at exposing the real error messages. |
I addressed this a bit in #3073. A hotfix is out, folks can test their builds again to be sure. |
This should be fixed, as this error was previously a generic one we threw, but now have fixed. |
Thank you all! |
Details
We were initially getting build failures over a configuration issue. I believed to have resolved the configuration, but there's no way to tell with the error message provided. The build linked above is from a Version I added against a branch, which is rolled back to our last known good commit for readthedocs, so it should succeed. It fails, and at this point I don't seem to have any way to successfully build my docs.
Expected Result
Either:
Actual Result
The build failed with the following: "Error: an unexpected error occurred". This error message gives me nothing to work with. I can't imagine its all that useful to a developer reading reports like this either. Searching the web for this issue is also useless, since every previous report is either a case that readthedocs devs identified as some problem that's reported as solved, or some user magically figuring out their issue was some configuration issue not relevant to my project.
The text was updated successfully, but these errors were encountered: