DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31965>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31965 cvs failonerror target fails even though there's no error ------- Additional Comments From [EMAIL PROTECTED] 2004-11-12 11:33 ------- I would suggest upgrading your cvs server and client and see if it helps. Adn you might want to do the cvs checkout using a script to check return code as well and see if it makes a difference compared to the java wrapper. I know historically that the cvs server code was known to run out of memory in case of huge update or checkout and not reporting correctly the error back to the client as it failed to handle correctly that situation. This can be made worse in case of huge binaries files as it RCS file can be muuuuch bigger than the file itself (look at the ,v files on your server) and to complicate things further the cvs server tries to load the whole module in memory when you checkout. A good way to put the machine on its knees. For more information on that matter, I suggest looking at that problem with the cvs people: https://www.cvshome.org/cyclic/cvs/dev-req.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
