This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Can not checkout production build sources | ||
---|---|---|---|
Product: | obsolete | Reporter: | rnovak <rnovak> |
Component: | collabnet | Assignee: | rnovak <rnovak> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 5.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
rnovak
2006-03-16 18:20:59 UTC
Pls investigate ASAP, thanks. Accepting the issue and started to work on it. Regards, Ramya Support Operations While support is investigating into this, can we at least get the project names (and the associated commands used) that cause this failure? I tried checking out a few projects, and am able to, hence wanted to get more information. In the interim we are checking for any issues on the site. Updating Status Whiteboard. Our production operations team have looked through the logs and don't see anything particular. Problems like this is hard to diagnose without some more detailed information. Is the user able to checkout any other projects? Is there only 1 user having this problem or everyone else having this problem? What is the name of the project, and what command is the user(s) using to checkout the project? Also, please provide the time line of when this error was encountered. Thanks We are not able to do any regular daily build of Netbeans. The first step of such build is check out of all the required sources. Here is an example of CVS command used for the check out: cvs -z6 -d :pserver:rbalada@cvs.netbeans.org:/cvs co -AP -rrelease50 "-D2006-03-16 20:30 +0000" ant apisupport autoupdate beans classfile clazz collab contrib core db debuggercore debuggerjpda diff editor extbrowser form html httpserver i18n ide image installer j2ee j2eeserver java javacvs javadoc jellytools jemmy jemmysupport junit lexer libs mdr metrics monitor nbbuild openide openidex performance projects properties refactoring schema2beans scripting serverplugins sysprops tasklist tomcatint translatedfiles usersguide utilities vcscore vcsgeneric versioncontrol web websvc xml xtest We usually use user "rbalada" The check out takes too long and fails. The error message is: cvs checkout: warning: unrecognized response ... followed by: cvs checkout: inflate: invalid stored block lengths cvs [checkout aborted]: reading from server: I/O error I tried the same command: ##-bash-2.05b$ cvs -z6 -d :pserver:asarkar@cvs.netbeans.org:/cvs co -AP -- rrelease0 -D"2006-03-16 20:30 +0000" ant apisupport autoupdate beans classfile clazz collab contrib core db debuggercore debuggerjpda diff editor extbrowser form html httpserver i18n ide image installer j2ee j2eeserver java javacvs javadoc jellytools jemmy jemmysupport junit lexer libs mdr metrics monitor nbbuild openide openidex performance projects properties refactoring schema2beans scripting serverplugins sysprops tasklist tomcatint translatedfiles usersguide utilities vcscore vcsgeneric versioncontrol web websvc xml xtest (Missed the 50 in the rrelease50, instead used release0) and was able to check out the entire stuff. Trying once more with -rrelease50. rnovak, I was able to checkout the entire source without any problems using the same command: cvs -z6 -d :pserver:karishma@cvs.netbeans.org:/cvs co -AP -rrelease50 -D "2006-03-16 20:30 +0000" ant apisupport autoupdate beans classfile clazz collab contrib core db debuggercore debuggerjpda diff editor extbrowser form html httpserver i18n ide image installer j2ee j2eeserver java javacvs javadoc jellytools jemmy jemmysupport junit lexer libs mdr metrics monitor nbbuild openide openidex performance projects properties refactoring schema2beans scripting serverplugins sysprops tasklist tomcatint translatedfiles usersguide utilities vcscore vcsgeneric versioncontrol web websvc xml xtest Can you please attach the last 50 lines of the cvs command, including the standard output and the error with this issue. This information would be helpful to check where its failing. There might be one particular project that's causing the problem and it would be good to know what that is, and the last 50 lines of the failed cvs command should tell us which project/file. Regards, Karishma Support Operations Thank you very much for your effort to investigate the problem. It seems it got resolved. From yesterday we are again able to do the full check out of Netbeans sources and produce production build. Since no issue was found at the server side it might have been a network problem between netbeans.org and our building machine. But this is also strange, because some CVS checkouts succeeded some especial longer ones didn't, depending on the list of modules that were checked out. We recently moved out from Collabnet's infrastructure |