-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Help with failing build needed (Neos/Flow) #2623
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
You have an invalid |
Ah, dang… completely forgot about that. That's what you get when a service runs for such a long time without issues… ;) Thanks! (Could I have seen that from the log output I has access to?) Problem now solved after a little detour: We did some juggling in the project so the documentation is at a different place in two branches, than it used to be. Can we set that per branch somehow? Because leaving it empty to have it found might as well pick up other For the record, here's how I solved it: since we split our mono-repo into multiple smaller ones, I changed the setup to point to a split repo and could point rftd.org to just |
We're trying to move more of our config over to a YAML file (http://docs.readthedocs.io/en/latest/yaml-config.html) -- but currently we haven't ported the There was an error in our reporting that hid how the missing |
Thanks! |
Details
Expected Result
I'd like to see the documentation build just fine.
Actual Result
The build fails, as shown at the build URL.
The problem is: I have no clue what is going on there and how we could fix this from our side, if we actually could fix it.
We have the same issue with "our other project" as can be seen at https://readthedocs.org/projects/neos/builds/
On top of that, the message looks like a hint to me, not like an error… so is this actually the cause for the error?
The text was updated successfully, but these errors were encountered: