ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31965] - cvs failonerror target fails even though there's no error
Date Fri, 12 Nov 2004 03:47:30 GMT
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 kevin.jackson@it.fts-vn.com  2004-11-12 03:47 -------
I'm not sure it's possible to get any more information out of this.  You've got
the return code and the actual command run against the repository.

You suspect it may be a timing issue - do you mean that the task times-out in
Ant, but not when run from the command line?

About the only extra instrumentation would be the time it takes to complete each
CVS command.  But that would only confirm your suspicion.  Is it a reproducable
bug - each time you check out a certain repository it fails, or does it occur
infrequently?  If it's infrequent then it may just be a network latency issue
with the amount of data you're trying to recieve.

I can't see very much that can be done inside the Ant code to help address this.
 One workaround would be to seperate the repository into small sub-projects and
check them out individually - this would again confirm if it's simply a time
issue for a command to complete.

Kev

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message