From: Erik P. <epe...@iv...> - 2014-03-27 02:46:31
|
On Wed, 26 Mar 2014, Maarten Brock wrote: > Well, I'm not sure it is a bug, but I can't create the linux i386 and > windows 32 bit release candidates from the snapshots because derna again > is not willing to build them. And I have no clue why it suddenly failed > again. I don't think I really changed anything. And I've restarted the > build on derna many times since. > > Maarten There have recently been failures across much of the DCF, including derna. In all of the systems that I have checked, subversion is frequently encountering errors checking out files from the Sourceforge repository (either "Unable to connect to repository" or "Network connection closed unexpectedly"). Since multiple computers around the world are having the same connection problems, I think this is a problem on Sourceforge's end. The script that starts the snapshot build process will try up to three times to checkout the sdcc-build tree. It might be useful to insert a delay into the script so that if there is a failure, it does not immediately try again (and immediately fail again). The other trees (sdcc-extra, sdcc-web, and sdcc) are checked out at various points by makefiles, and don't have any error retry recovery logic at all (this is handled in sdcc-build/lib/fetch.mk) so depending on which part fails you may end up with a complete package but without any regression testing, a partial package, or an empty package. I'm behind on a number of my other commitments, so while I'd like to make the checkout process in the snapshot builds more robust, it probably won't be very soon. At the moment my best suggestion is just to retry the build. Either Sourceforge's infrastructure problem will be fixed or you might be lucky with successful checkouts (as can be seen on the snapshot page, there are still successful builds, so this isn't just a forlorn hope). Erik |