From: David S. <sa...@mi...> - 2006-03-15 16:18:56
|
All, I've submitted a SourceForge support request about intermittent CVS pserver access: http://sourceforge.net/tracker/index.php?func=detail&aid=1450494&group_id=1&atid=200001 SourceForge believes that a similar problem was resolved on the 12th: http://sourceforge.net/tracker/index.php?func=detail&aid=1447585&group_id=1&atid=200001 At least two independent sources have complained about CVS here since the 12th. Can you confirm that your problems occurred on the 13th or later? Thanks, David Saff |
From: David S. <sa...@mi...> - 2006-03-16 18:21:35
|
All, I've heard back from SourceForge. Some quotes from below: >>>>>> Per the site status page: ( 2006-03-13 12:42:16 - Project CVS Service ) As of 2006-03-12 pserver (anonymous) CVS services, along with tarballs and ViewCVS are down for projects that start with the letters e, i, j, o, v, w and x. We hope to resolve this issue in the next 2 days. Please keep an eye there for further updates to this issue. [snip] However, the CVS issues we have been having are generally hardware related. We are working on swapping out the hardware and attempting to isolate the causes, but this takes time to do, and given the infrastructure and volume of use, we'd prefer to keep it up, even if only limping, than take it down for a complete overhaul. <<<<<< It looks like our options are to sit and wait, or change the name of the project to UnitJ. No guarantees were made about subversion speed, so if we decided to change to SVN, it would not necessarily be for long-term reliability. Thanks, David Saff -------- Original Message -------- Subject: [ alexandria-Support Requests-1450494 ] CVS services issue Date: Thu, 16 Mar 2006 06:28:55 -0800 From: SourceForge.net <no...@so...> To: no...@so... Support Requests item #1450494, was opened at 2006-03-15 11:14 Message generated for change (Comment added) made by burley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200001&aid=1450494&group_id=1 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Project CVS Services Group: None >Status: Closed Priority: 5 Submitted By: David Saff (dsaff) >Assigned to: David Burley (burley) >Summary: CVS services issue Initial Comment: Dear SourceForge, Over the last few months, public anonymous access to JUnit CVS has become so slow and unreliable that it has slowed the pace at which we are able to accept patches and support early adopters. Is there anything we or you can do to solve this problem? Are the subversion servers faster? Will the subversion servers stay fast if many people switch over? Below is a sampling of independent mailing list messages indicating the kinds of problems seen. Thanks, David Saff 2006/03/15: "I attempted to check out the current CVS HEAD, but the system was unresponsive." 2006/03/14: "I will send Javadoc updates for the classes as soon as cvs.sourceforge.net stops timing out :-(. It usually works when America is asleep (in the morning over here) ...." 2006/03/08: "is it just me or do you guys also get lots of timeouts when trying to synchronize with the sourceforge cvs?" 2005/10/24: "I have found the SourceForge CVS server _extremely_ sluggish and unreliable." 2005/09/14: "I get varying errors depending on the client, but they seem to all be related to either the CVS server timing out or the connection being refused." ---------------------------------------------------------------------- >Comment By: David Burley (burley) Date: 2006-03-16 09:28 Message: Logged In: YES user_id=597273 Greetings, Per the site status page: ( 2006-03-13 12:42:16 - Project CVS Service ) As of 2006-03-12 pserver (anonymous) CVS services, along with tarballs and ViewCVS are down for projects that start with the letters e, i, j, o, v, w and x. We hope to resolve this issue in the next 2 days. Please keep an eye there for further updates to this issue. Regarding SVN, I am not sure even the SVN developers themselves can answer that question. I am not aware of a SVN installation with a potential to grow as large as the one we are hosting is. While we have gone to great lengths to ensure its scalable and do not believe there will be issues with it (SVN is much easier to scale than CVS), only time will tell. Regarding performance, CVS is actually faster. There's less overhead in a CVS operation than there is in a SVN operation, but, our SVN offering has been more stable of late, so that may be reason enough to consider it. However, the CVS issues we have been having are generally hardware related. We are working on swapping out the hardware and attempting to isolate the causes, but this takes time to do, and given the infrastructure and volume of use, we'd prefer to keep it up, even if only limping, than take it down for a complete overhaul. We know these issues have been around for a long time, and we have been working an equally long amount of time to fix them. We think we'll be over the hump shortly and CVS performance will go back to expected levels then. Thank you, David Burley Quality of Service Analyst, SourceForge.net ---------------------------------------------------------------------- Comment By: David Saff (dsaff) Date: 2006-03-15 11:55 Message: Logged In: YES user_id=325156 An interesting recent development: Yes. I can observe it right now. If I attempt to log in to an arbitrary SourceForge project cvs -d:pserver:ano...@cv...:/cvsroot/ant-contrib I get an immediate completion after hitting enter on the password. If I change it to: cvs -d:pserver:ano...@cv...:/cvsroot/junit I get "Unrecognized auth response from cvs.sourceforge.net: M PserverBackend: PserverBackend() Connect (Connection Timed Out)". Could this be a problem only with JUnit's repository? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=200001&aid=1450494&group_id=1 |
From: Curt A. <ca...@ap...> - 2006-03-15 17:39:12
|
On Mar 15, 2006, at 10:58 AM, David Saff wrote: > Curt Arnold wrote: >> Yes. I can observe it right now. If I attempt to log in to an >> arbitrary SourceForge project >> >> cvs -d:pserver:ano...@cv...:/cvsroot/ant-contrib >> >> I get an immediate completion after hitting enter on the >> password. If I change it to: >> >> cvs -d:pserver:ano...@cv...:/cvsroot/junit >> >> I get "Unrecognized auth response from cvs.sourceforge.net: M >> PserverBackend: PserverBackend() Connect (Connection Timed Out)". > > Woah. I had never considered that this might be a JUnit-only > problem. I've followed up with SourceForge. > I'm still seeing the problem, but Gump just successfully built junit. >> When reviewing earlier Gump logs, I noticed that the junit build >> also had timed out due to CVS. Gump is currently running and >> junit has not been attempted yet, but you could review the status >> at http://vmgump.apache.org/gump/public/buildLog.html. I noticed >> that the Gump nag notices are sent to you personally, so maybe you >> have something in those that could provide info on the status of >> anonymous CVS access on previous runs. > > I have yet to receive any kind of automated nag, only personal nags > from real people. Could something be misconfigured? Thanks, > Possibly, you should have been receiving Gump failure messages just before 10-March-2006 since Gump is indicating that the start of the current success state started then. The nag element in your project descriptor is unusual, it seems to be the only one in the Gump universe that places contains < in the to address (it is common in the from address). It is also common that nag messages are sent to the development list. Since messages from non-subscribers are usually blocked for moderation, it would be good to either make the message appear to be from a current subscriber. I think using ge...@gu... (the Gump general mailing list) as a sender is undesirable since it results in spurious replies to the nag message going to their general list. The current project descriptor contains: <nag from="Gump Integration <ge...@gu...>" to="David Saff <sa...@mi...>" /> I could change it to: <nag from="David Saff <sa...@mi...>" to="jun...@li..." /> or post a request to the Gump mailing list to review your project descriptor. |
From: David S. <sa...@mi...> - 2006-03-15 17:55:26
|
Curt Arnold wrote: > The current project descriptor contains: > > <nag from="Gump Integration <ge...@gu...>" > to="David Saff <sa...@mi...>" /> > > I could change it to: > > <nag from="David Saff <sa...@mi...>" > to="jun...@li..." /> > > or post a request to the Gump mailing list to review your project > descriptor. I have no knowledge of Gump nag descriptor formatting, so I'll have to ask your help on this. How often are the nag messages sent? If it's daily or less, then sending it to junit-devel should be fine. Otherwise, please have it sent straight to me. Thanks, David Saff |
From: Curt A. <ca...@ap...> - 2006-03-15 18:03:40
|
On Mar 15, 2006, at 11:55 AM, David Saff wrote: > I have no knowledge of Gump nag descriptor formatting, so I'll have > to ask your help on this. How often are the nag messages sent? If > it's daily or less, then sending it to junit-devel should be fine. > Otherwise, please have it sent straight to me. Thanks, Daily messages when junit is failing to build, no messages otherwise. I'll post a request on the issue to ge...@gu.... |
From: Curt A. <ca...@ap...> - 2006-03-15 18:00:29
|
>> >> I have yet to receive any kind of automated nag, only personal >> nags from real people. Could something be misconfigured? Thanks, >> > I've reviewed the Gump mailing list. There were CVS problems and junit build problems reported on 09-March-2006 (http:// marc.theaimsgroup.com/?l=gump&m=114190474119176&w=2) which went into the "All dressed up and no where to go" message for undeliverable failure messages. The following fragments were significant for junit: The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/junit/gump_work/update_junit.html Work Name: update_junit (Type: Update) Work ended in a state of : Failed Elapsed: Command Line: cvs -q -z3 -d :pserver:ano...@cv...:/ cvsroot/junit \ update -P -d -A [Working Directory: /usr/local/gump/public/workspace/ cvs/junit] --------------------------------------------- cvs [update aborted]: end of file from server (consult above messages if any) --------------------------------------------- The previous day's message (http://marc.theaimsgroup.com/? l=gump&m=114181866415173&w=2) had a successful CVS checkout, but failed with: versiontag: BUILD FAILED /x1/gump/public/workspace/junit/build.xml:21: Warning: Could not find file /x1/gump/public/workspace/junit/junit/runner/ Version.java.template to copy. You agreed to let yourself be nagged about Gump failures on 12- Mar-2006 and the Gump descriptor for junit was changed by bil...@ap.... Though the to address is unusual, maybe it is acceptable. Since the change occurred after the last reported failure, maybe it will work just fine when the next failure message comes along. I'll raise this on ge...@gu... and take no action myself. |
From: David S. <sa...@mi...> - 2006-03-15 18:04:17
|
Curt Arnold wrote: > BUILD FAILED > /x1/gump/public/workspace/junit/build.xml:21: Warning: Could not find > file > /x1/gump/public/workspace/junit/junit/runner/Version.java.template to > copy. Yes. That has since been fixed in HEAD. > You agreed to let yourself be nagged about Gump failures on > 12-Mar-2006 and the Gump descriptor for junit was changed by > bil...@ap.... Though the to address is unusual, maybe it is > acceptable. Since the change occurred after the last reported > failure, maybe it will work just fine when the next failure message > comes along. I'll raise this on ge...@gu... and take no > action myself. Sounds like the right plan. Thanks, David Saff |