-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Build not executed & repo error #318
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
By the way - before I've deleted the project, I received no error and the task was not showing up in my build list. But I saw it on |
Do you have problems with your service at all and I got the stuff from varnish?
Same with Ctrl+F5, so it's not a browser cache issue (and maybe your varnish is configured to respect the cache control headers, if yes, you know it's not a varnish issue) |
I've read that in the docs - but I don't think it's the root cause. Maybe the CSS issue is a sideeffect of particular cache updates on a not existing page. No, that sounds not really like my problem. I don't see a triggered state somewhere (only in the |
Looks like your docs might not be on both of the webheads, because random components of your docs aren't loading sometimes it is css sometimes it is the document itself. I'll force a rebuild and see what happens. |
Oh, yeah, it looks like because you named it the same there are some left overs on one of the webheads. I'll open a ticket about that. I'll also try cleaning things out on the server. You may have to import your project again but I'll try to avoid that. |
Maybe a cronjob that is taking care for ghost processes and your build system and kill them might help since many others seem to have the same issue. I did that a few months ago on a heavily used CI server - that solved my problem (but you need statistics about how long some the most processes are living - otherwise you'll kill active builds). If it's easier for you, simply kick out that project - I removed and re-imported it previously anyways, so nothing important is there. |
Well, the jobs I think have a limitation on themselves, being left in a triggered state doesn't mean it is necessarily waiting to be built, if it died while in some initial stages (due to an error in checkout that was fatal or the like) it will leave the build as 'triggered' in the DB even though it isn't. @ericholscher is far better at debugging these things in the system than I am, I am merely a caretaker when he is out of town. |
Ah, it's building :-) |
And it's broken again :-( |
Yes, I am working on it. I'll let you know if/when I need some more information from you. |
Ok, cleaned out he environement completely, then force updated the project and it appears to be working. Please go through your docs to make sure everything is working, if so, close this. |
Everything is fine again, thanks! |
The table of contents is gone in the PDF version - it looks like everything else is fine. |
Did you look at the PDF build data? https://readthedocs.org/builds/zend-server-api/375732/ looks like some latex issues. PDF building with sphinx is finicky, have you verified it works locally? I don't have any advice for this, I've never used the PDF version that sphinx can generate. |
Mh, looks like a diplicated identifier. So not related - thanks again :) |
Cleaning out the environment simply means to delete all the artifacts in the user_builds directory for the project. |
Hey,
I had a problem a few hours ago, that I was not able to build the docs of my project.
After a few tries (manual build, build via hook, manual triggered hook) I've deleted the project and wanted to re-import it. After I did that, I got the error
There are no builds for this project. Is the repo correct?
- but it was exactly what it was before. I tried also the git, ssh and http way to access the repo, nothing is working. The old docs are still online, so it was working (these are the docs, I've builded before the project was deleted): https://zend-server-api.readthedocs.org/en/latest/Maybe a problem because of the name? I've choosen the same as before.
Hopefully you'll find the time to look into it.
P.S.: thanks for the great service 👍
The text was updated successfully, but these errors were encountered: