Re: [Junit-devel] SourceForge CVS

[Curt A. <ca...@ap...>]

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 &lt;ge...@gu...&gt;"
          to="David Saff &lt;sa...@mi...&gt;" />

I could change it to:

     <nag from="David Saff &lt;sa...@mi...&gt;"
               to="jun...@li..." />

or post a request to the Gump mailing list to review your project  
descriptor.